Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5b80a3dc40ccb7ac1b301ff5e706b33b1528b44d98cc49982fd0372807c322e

Tx prefix hash: 266df39d259688c6a06aab3e5bed767853501a2b8f43792c5e9edf958eab8bc3
Tx public key: 14576f57f92961407ff5cab5426d28c8c0c5c9d99af2d91bddd4329e3eccab85
Timestamp: 1766253608 Timestamp [UCT]: 2025-12-20 18:00:08 Age [y:d:h:m:s]: 00:001:19:03:04
Block: 1437887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1283 RingCT/type: yes/0
Extra: 0114576f57f92961407ff5cab5426d28c8c0c5c9d99af2d91bddd4329e3eccab8502110000000970609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25448af7dddcef1d125ae357465ac7b7bbb92c7bf8e6e8c284cf61f8e69d87da 0.600000000000 1926700 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": 1437897, "vin": [ { "gen": { "height": 1437887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25448af7dddcef1d125ae357465ac7b7bbb92c7bf8e6e8c284cf61f8e69d87da" } } ], "extra": [ 1, 20, 87, 111, 87, 249, 41, 97, 64, 127, 245, 202, 181, 66, 109, 40, 200, 192, 197, 201, 217, 154, 242, 217, 27, 221, 212, 50, 158, 62, 204, 171, 133, 2, 17, 0, 0, 0, 9, 112, 96, 157, 3, 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