Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f52938383323ff31e38509cc960d75d5f490da7fdb096e66954fb6c03ffbadf7

Tx prefix hash: 668c6a00627021b4dbb4a5f446df4b9b4fc59fd0a2cf16051d918e9f3b14fbdf
Tx public key: c45bcb4f525ad64e865321e489fdbb67282c322513d3e127a5b9a01e10fd9f96
Timestamp: 1732204258 Timestamp [UCT]: 2024-11-21 15:50:58 Age [y:d:h:m:s]: 00:002:14:02:29
Block: 1158636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1850 RingCT/type: yes/0
Extra: 01c45bcb4f525ad64e865321e489fdbb67282c322513d3e127a5b9a01e10fd9f960211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ef58cba21aaba6408ce97b5e86e5441c5057f584aa68a7e25d2e2cf14d01ecf 0.600000000000 1644265 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": 1158646, "vin": [ { "gen": { "height": 1158636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ef58cba21aaba6408ce97b5e86e5441c5057f584aa68a7e25d2e2cf14d01ecf" } } ], "extra": [ 1, 196, 91, 203, 79, 82, 90, 214, 78, 134, 83, 33, 228, 137, 253, 187, 103, 40, 44, 50, 37, 19, 211, 225, 39, 165, 185, 160, 30, 16, 253, 159, 150, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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