Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b20e016f1c1514fe53f49bba68019bf06df26fe766ff5f3ab5a7fd1e3d0a796

Tx prefix hash: 64842b4afbe37f5bcaccc45c7708ccdc60f12caf6b57c660c0fd260b907df992
Tx public key: e28e9890e19e7f68d76e1a8d558a1a98a49d04f6852f05c8874b053a9bbbf560
Timestamp: 1736287079 Timestamp [UCT]: 2025-01-07 21:57:59 Age [y:d:h:m:s]: 00:296:03:51:16
Block: 1192446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209170 RingCT/type: yes/0
Extra: 01e28e9890e19e7f68d76e1a8d558a1a98a49d04f6852f05c8874b053a9bbbf560021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a205dec32491d8d3330d34bb1046e3f4e41da088041ebe46e0ccac9d11969332 0.600000000000 1678999 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": 1192456, "vin": [ { "gen": { "height": 1192446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a205dec32491d8d3330d34bb1046e3f4e41da088041ebe46e0ccac9d11969332" } } ], "extra": [ 1, 226, 142, 152, 144, 225, 158, 127, 104, 215, 110, 26, 141, 85, 138, 26, 152, 164, 157, 4, 246, 133, 47, 5, 200, 135, 75, 5, 58, 155, 187, 245, 96, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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