Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f64ddec3ef69cd0c8cb8c6def02112ed655b77f57bcf6f5d9eb5a7378c1a508

Tx prefix hash: ef2296b5fbb0f13b0f606551ae611c0dd5b39afd6342447133dd8c8c0134d8f9
Tx public key: d567996cb49a8fd4da3a7c5ee8dd8a64239efd81c2dd8b1699bc14675a992762
Timestamp: 1765300558 Timestamp [UCT]: 2025-12-09 17:15:58 Age [y:d:h:m:s]: 00:014:02:59:18
Block: 1429978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10117 RingCT/type: yes/0
Extra: 01d567996cb49a8fd4da3a7c5ee8dd8a64239efd81c2dd8b1699bc14675a99276202110000000670609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e5586e97a2d984adb3bac7f48d6de1bd43ff509f128891bb43528ce08ecd8ac 0.600000000000 1918711 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": 1429988, "vin": [ { "gen": { "height": 1429978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e5586e97a2d984adb3bac7f48d6de1bd43ff509f128891bb43528ce08ecd8ac" } } ], "extra": [ 1, 213, 103, 153, 108, 180, 154, 143, 212, 218, 58, 124, 94, 232, 221, 138, 100, 35, 158, 253, 129, 194, 221, 139, 22, 153, 188, 20, 103, 90, 153, 39, 98, 2, 17, 0, 0, 0, 6, 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