Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b13c31711481ffda5e0126d07045a63c369410c7dd291bbda7794c0f49c1012

Tx prefix hash: ec0841a68d1c02a2adefb6a0167490c4072366b09a89ba1bc0cc5e8e915ebc29
Tx public key: 60628a42b4f3d6b47ae9a2d7fa01a4e80279feefbcf770935565f5fbc3cd3973
Timestamp: 1715487301 Timestamp [UCT]: 2024-05-12 04:15:01 Age [y:d:h:m:s]: 00:284:07:47:06
Block: 1020178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203160 RingCT/type: yes/0
Extra: 0160628a42b4f3d6b47ae9a2d7fa01a4e80279feefbcf770935565f5fbc3cd397302110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c12d986fad66dc8bb6ca834352703f34c413476af07cb34c1b51dcc023d6b45e 0.600000000000 1484239 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": 1020188, "vin": [ { "gen": { "height": 1020178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c12d986fad66dc8bb6ca834352703f34c413476af07cb34c1b51dcc023d6b45e" } } ], "extra": [ 1, 96, 98, 138, 66, 180, 243, 214, 180, 122, 233, 162, 215, 250, 1, 164, 232, 2, 121, 254, 239, 188, 247, 112, 147, 85, 101, 245, 251, 195, 205, 57, 115, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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