Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9b1de7222de6e671813ece2f53f554edb3e43d5806df56b8552e36852843296

Tx prefix hash: 432fc09edd090a34e0a5d7b8fd16f565da8aa383c48a069a0a9750c472fc8fc3
Tx public key: 60d54aa2e8f39c9af3e6b508e2ecc303e44b186d2765fe96a9e4a70f41b5150d
Timestamp: 1755189724 Timestamp [UCT]: 2025-08-14 16:42:04 Age [y:d:h:m:s]: 00:052:08:35:14
Block: 1346773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36902 RingCT/type: yes/0
Extra: 0160d54aa2e8f39c9af3e6b508e2ecc303e44b186d2765fe96a9e4a70f41b5150d0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 162cab0d8048a748d14d277932c1df70882d8c21d025f0931f16079f3bb41294 0.600000000000 1834678 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": 1346783, "vin": [ { "gen": { "height": 1346773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "162cab0d8048a748d14d277932c1df70882d8c21d025f0931f16079f3bb41294" } } ], "extra": [ 1, 96, 213, 74, 162, 232, 243, 156, 154, 243, 230, 181, 8, 226, 236, 195, 3, 228, 75, 24, 109, 39, 101, 254, 150, 169, 228, 167, 15, 65, 181, 21, 13, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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