Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32e4749254fe32cdf4c166dae5665cf5e43854ead8a469ec5b90a34d649a78d9

Tx prefix hash: 590ded684d5563b2bfe3417e2adf9b3eb85f4f7502d3e615934f0cc36eae0054
Tx public key: 9796227b21470a7d598b8fdc877c907cc3a4db480f59b74b03b2c17cf363cb7c
Timestamp: 1726013662 Timestamp [UCT]: 2024-09-11 00:14:22 Age [y:d:h:m:s]: 00:074:06:46:20
Block: 1107412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53107 RingCT/type: yes/0
Extra: 019796227b21470a7d598b8fdc877c907cc3a4db480f59b74b03b2c17cf363cb7c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8937e3941b7bc901fb29f1d6a7948b492e4af485c63b554cddd08b5d679346f5 0.600000000000 1585023 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": 1107422, "vin": [ { "gen": { "height": 1107412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8937e3941b7bc901fb29f1d6a7948b492e4af485c63b554cddd08b5d679346f5" } } ], "extra": [ 1, 151, 150, 34, 123, 33, 71, 10, 125, 89, 139, 143, 220, 135, 124, 144, 124, 195, 164, 219, 72, 15, 89, 183, 75, 3, 178, 193, 124, 243, 99, 203, 124, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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