Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aef7ef9d7480941b0dbd03413dcf0ad309bdf581fa646195594160870f3c101

Tx prefix hash: d69de43ce4d14521e5397f5b7adc4612060ba8d6c9a28f04afa8678c8c11ab6a
Tx public key: 409d0ba2e8c04723936f9f80af1b9ccbcc5d626d3d8fa3a34ae7d58a74582cad
Timestamp: 1751996712 Timestamp [UCT]: 2025-07-08 17:45:12 Age [y:d:h:m:s]: 00:124:06:38:21
Block: 1321450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87270 RingCT/type: yes/0
Extra: 01409d0ba2e8c04723936f9f80af1b9ccbcc5d626d3d8fa3a34ae7d58a74582cad02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5be46a434b362acf5b9552261d14beab1ec2dc448dca04ee07789fcea46efd47 0.600000000000 1809157 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": 1321460, "vin": [ { "gen": { "height": 1321450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5be46a434b362acf5b9552261d14beab1ec2dc448dca04ee07789fcea46efd47" } } ], "extra": [ 1, 64, 157, 11, 162, 232, 192, 71, 35, 147, 111, 159, 128, 175, 27, 156, 203, 204, 93, 98, 109, 61, 143, 163, 163, 74, 231, 213, 138, 116, 88, 44, 173, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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