Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 602e0ac40ce5c0ead0ce04aa6c0ac097a8c12d60425e519ec04a37be951dda38

Tx prefix hash: 689a956f6993a67f570f047e0bae7a7d235dd87e7a9b415a362aef34b84dbb47
Tx public key: 0ecb75c6ac895eff484f149e279ce58efca50789623ba2709bbb795a068ed0dd
Timestamp: 1630691924 Timestamp [UCT]: 2021-09-03 17:58:44 Age [y:d:h:m:s]: 03:222:17:23:48
Block: 326755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 933777 RingCT/type: yes/0
Extra: 010ecb75c6ac895eff484f149e279ce58efca50789623ba2709bbb795a068ed0dd021100000024baa4486c000000000000000000

1 output(s) for total of 50.739082871000 dcy

stealth address amount amount idx
00: c3146a6fab1827ff0bf6d2c7e7fdda3d86957226f76b621efa25571d1fcf0a83 50.739082871000 676914 of 0

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": 326765, "vin": [ { "gen": { "height": 326755 } } ], "vout": [ { "amount": 50739082871, "target": { "key": "c3146a6fab1827ff0bf6d2c7e7fdda3d86957226f76b621efa25571d1fcf0a83" } } ], "extra": [ 1, 14, 203, 117, 198, 172, 137, 94, 255, 72, 79, 20, 158, 39, 156, 229, 142, 252, 165, 7, 137, 98, 59, 162, 112, 155, 187, 121, 90, 6, 142, 208, 221, 2, 17, 0, 0, 0, 36, 186, 164, 72, 108, 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