Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82b0e36b8336596d80272092ac1b7e9aad2419a47dd909ca1da4c5ce8cb8dbd9

Tx prefix hash: 98e5c1bc87ed0d5ec51bb36d88c0b6eb9ec79d340995b815bb0563ae6025195e
Tx public key: e2df35e4c1f1de2096e313ac12ebfa7ba2cf7f57360b5fec75072d62e75117d3
Timestamp: 1705666763 Timestamp [UCT]: 2024-01-19 12:19:23 Age [y:d:h:m:s]: 01:077:05:52:21
Block: 938694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316315 RingCT/type: yes/0
Extra: 01e2df35e4c1f1de2096e313ac12ebfa7ba2cf7f57360b5fec75072d62e75117d30211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97b4849f1033a9f07243a7983d915263ed58cfc2c1b1c74acacdc7494210d3af 0.600000000000 1396766 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": 938704, "vin": [ { "gen": { "height": 938694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97b4849f1033a9f07243a7983d915263ed58cfc2c1b1c74acacdc7494210d3af" } } ], "extra": [ 1, 226, 223, 53, 228, 193, 241, 222, 32, 150, 227, 19, 172, 18, 235, 250, 123, 162, 207, 127, 87, 54, 11, 95, 236, 117, 7, 45, 98, 231, 81, 23, 211, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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