This is probably caused by multiple CKB addresses are mapped to the same BTC address, and these CKB addresses are revealed in the same transaction, so this transaction is loaded multiple times by different CKB addresses.
E.g. CKB Addresses A, B, C are all mapped to BTC address D, when the transaction list is filtered by D, it's actually filtered by A | B | C. If there is a transaction like
A -> C
B -> C
It will be indexed by A, B, C, respectively, thus 3 transactions are returned.
Page: https://pudge.explorer.nervos.org/xudt/0x7337d2075479d5c6789564516be1db11478e1d3ca70ad88050fe0bf3ff05acc2?filter=tb1ppavy0ekqk3mur37zvhqje0smauqa523tnrccynzlya5hkxy75nrqcfntth
This is probably caused by
multiple CKB addresses are mapped to the same BTC address, and these CKB addresses are revealed in the same transaction
, so this transaction is loaded multiple times by different CKB addresses.E.g. CKB Addresses
A
,B
,C
are all mapped to BTC addressD
, when the transaction list is filtered byD
, it's actually filtered byA | B | C
. If there is a transaction likeIt will be indexed by
A
,B
,C
, respectively, thus 3 transactions are returned.