Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f99a40317dcb80ed65071fbd0fbbd9caa33c1cf52acb768c171b084c24509e3d

Tx prefix hash: cc7cad301e45e7bd3f457cbd65f6e0a9bde1ce4b998fe9e0a4c6750f52e81359
Tx public key: 52617a3d760ebb4873dfc799c25e47e7c895ad53d4af1f7aa02c68d16578403e
Timestamp: 1722345632 Timestamp [UCT]: 2024-07-30 13:20:32 Age [y:d:h:m:s]: 00:269:01:32:05
Block: 1077000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192217 RingCT/type: yes/0
Extra: 0152617a3d760ebb4873dfc799c25e47e7c895ad53d4af1f7aa02c68d16578403e021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6330f6bdefcc83916398a931671b7720dcf7d1850a6e7233d7040d185df576d7 0.600000000000 1549543 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1077010, "vin": [ { "gen": { "height": 1077000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6330f6bdefcc83916398a931671b7720dcf7d1850a6e7233d7040d185df576d7" } } ], "extra": [ 1, 82, 97, 122, 61, 118, 14, 187, 72, 115, 223, 199, 153, 194, 94, 71, 231, 200, 149, 173, 83, 212, 175, 31, 122, 160, 44, 104, 209, 101, 120, 64, 62, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8