Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b96ec33618df4a74125c473a981d89a1284a4b661e6541f5e6dbab6f8dff38f3

Tx prefix hash: 930f17152835083cd6c8ecb4aa95edb93e1197bce2ee15654265698badd7415a
Tx public key: 0b52b57f4bf930cd5071dfe0192d5b765799b0fb28fb0083ebec8c9ec0e3da5b
Timestamp: 1755485199 Timestamp [UCT]: 2025-08-18 02:46:39 Age [y:d:h:m:s]: 00:138:21:49:07
Block: 1348907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99206 RingCT/type: yes/0
Extra: 010b52b57f4bf930cd5071dfe0192d5b765799b0fb28fb0083ebec8c9ec0e3da5b02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95ccaad7c32a460f8310d28e4f0d97d2842af1c3e84bb7399dfcbaa06e38c954 0.600000000000 1836836 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": 1348917, "vin": [ { "gen": { "height": 1348907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95ccaad7c32a460f8310d28e4f0d97d2842af1c3e84bb7399dfcbaa06e38c954" } } ], "extra": [ 1, 11, 82, 181, 127, 75, 249, 48, 205, 80, 113, 223, 224, 25, 45, 91, 118, 87, 153, 176, 251, 40, 251, 0, 131, 235, 236, 140, 158, 192, 227, 218, 91, 2, 17, 0, 0, 0, 3, 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