Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14126342a415f743026695aa16df424d3426f956905bfb90f5c7abbb98dc5a28

Tx prefix hash: 424b4634f801258a9dd0e7684dbccc115dcb059884060aaacc72b4afb6ef4ef7
Tx public key: 14ac3ccf6bf83a114e184e9f4b6bc6cc21a845dba08cb8d3c3f767960d80242f
Timestamp: 1757752032 Timestamp [UCT]: 2025-09-13 08:27:12 Age [y:d:h:m:s]: 00:142:07:14:00
Block: 1367420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101724 RingCT/type: yes/0
Extra: 0114ac3ccf6bf83a114e184e9f4b6bc6cc21a845dba08cb8d3c3f767960d80242f021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20c9ea8b8419294a2335375b5d8068837efb59b3d8770df41351f7842685af04 0.600000000000 1855459 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": 1367430, "vin": [ { "gen": { "height": 1367420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20c9ea8b8419294a2335375b5d8068837efb59b3d8770df41351f7842685af04" } } ], "extra": [ 1, 20, 172, 60, 207, 107, 248, 58, 17, 78, 24, 78, 159, 75, 107, 198, 204, 33, 168, 69, 219, 160, 140, 184, 211, 195, 247, 103, 150, 13, 128, 36, 47, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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