Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef66b222e2623089ce5ba8323b6f5de604cc2f11358425ab310d03d9b507dfb

Tx prefix hash: 45dfc263806175a3fe4d1563eb2f5cd38b1212128e760da4e8ef9b5816ed7d9d
Tx public key: 2315747046c791233a8b2df8a93a4fd1023c01ebd82337759e09442e628b28d3
Timestamp: 1710942137 Timestamp [UCT]: 2024-03-20 13:42:17 Age [y:d:h:m:s]: 01:070:14:15:38
Block: 982486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311450 RingCT/type: yes/0
Extra: 012315747046c791233a8b2df8a93a4fd1023c01ebd82337759e09442e628b28d302110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afe376ba20d1a1fbe28a1d5dee2c705716f12bc84fc36214cd1452045e1e18fc 0.600000000000 1442591 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": 982496, "vin": [ { "gen": { "height": 982486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afe376ba20d1a1fbe28a1d5dee2c705716f12bc84fc36214cd1452045e1e18fc" } } ], "extra": [ 1, 35, 21, 116, 112, 70, 199, 145, 35, 58, 139, 45, 248, 169, 58, 79, 209, 2, 60, 1, 235, 216, 35, 55, 117, 158, 9, 68, 46, 98, 139, 40, 211, 2, 17, 0, 0, 0, 11, 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