Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6c251679c896197640e90a806aedc617deaa7b8a60cc00faf164d23b75e4e41

Tx prefix hash: 8589db144eba8bd385a749f876f570d9b8e58e3af17c73c4362001f7bca4c503
Tx public key: 033c8e7617f720c79c5dc0eef7d1f6850f3010f2dc0c6246b1e1137778166b47
Timestamp: 1760483386 Timestamp [UCT]: 2025-10-14 23:09:46 Age [y:d:h:m:s]: 00:025:09:19:31
Block: 1390065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18176 RingCT/type: yes/0
Extra: 01033c8e7617f720c79c5dc0eef7d1f6850f3010f2dc0c6246b1e1137778166b470211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0c605b12f50286fd77536eaaf143eafa71b07413189f92cced0cb64e17aca79 0.600000000000 1878296 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": 1390075, "vin": [ { "gen": { "height": 1390065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0c605b12f50286fd77536eaaf143eafa71b07413189f92cced0cb64e17aca79" } } ], "extra": [ 1, 3, 60, 142, 118, 23, 247, 32, 199, 156, 93, 192, 238, 247, 209, 246, 133, 15, 48, 16, 242, 220, 12, 98, 70, 177, 225, 19, 119, 120, 22, 107, 71, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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