Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9d4f31ac7ea4299573eec890da8ee4718c30e7c1c5ce6061f01224f81f38d96

Tx prefix hash: 1967f0000f465b557296c9204077a94021884784ff2d3174888a6646edad2c80
Tx public key: 009260d3aa771d1b5c21b8611a9c6a03114d271936cfdf09484257b822e3772d
Timestamp: 1715237751 Timestamp [UCT]: 2024-05-09 06:55:51 Age [y:d:h:m:s]: 00:341:06:45:13
Block: 1018080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243948 RingCT/type: yes/0
Extra: 01009260d3aa771d1b5c21b8611a9c6a03114d271936cfdf09484257b822e3772d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bce3a80c5cf7f9ff02378b7f9b6c0abd2fdcbfd4de346b0819a95ec66c3fba1f 0.600000000000 1481865 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": 1018090, "vin": [ { "gen": { "height": 1018080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bce3a80c5cf7f9ff02378b7f9b6c0abd2fdcbfd4de346b0819a95ec66c3fba1f" } } ], "extra": [ 1, 0, 146, 96, 211, 170, 119, 29, 27, 92, 33, 184, 97, 26, 156, 106, 3, 17, 77, 39, 25, 54, 207, 223, 9, 72, 66, 87, 184, 34, 227, 119, 45, 2, 17, 0, 0, 0, 4, 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