Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45d7b1fb3a11dc193730e5441db91a802713d284f2001b49abe2aab8c4b1dec8

Tx prefix hash: ae31c264a8b453474842cf7ea23bbbf8d0f6b78de62fa0db8a5a06f5169c1d45
Tx public key: e9e3f60e351ae8ea9c46c6692bcdff99ac6006bb91dddf48472a968e9963efcb
Timestamp: 1733237374 Timestamp [UCT]: 2024-12-03 14:49:34 Age [y:d:h:m:s]: 00:029:02:04:29
Block: 1167198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20805 RingCT/type: yes/0
Extra: 01e9e3f60e351ae8ea9c46c6692bcdff99ac6006bb91dddf48472a968e9963efcb0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aba859b21fa209f4c241b019cc81e55f67638ce97e83e4f511e7565c13b8424 0.600000000000 1652893 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": 1167208, "vin": [ { "gen": { "height": 1167198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aba859b21fa209f4c241b019cc81e55f67638ce97e83e4f511e7565c13b8424" } } ], "extra": [ 1, 233, 227, 246, 14, 53, 26, 232, 234, 156, 70, 198, 105, 43, 205, 255, 153, 172, 96, 6, 187, 145, 221, 223, 72, 71, 42, 150, 142, 153, 99, 239, 203, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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