Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f353f326396e4cafbf462f839d645df86c1abbd734cbc53803813dfd1c22d90c

Tx prefix hash: ff3b34038527480b406f068185c2bed49706882021c3fec335cd539234a1c31d
Tx public key: 9df4ec23b0ae52605b23b9e8c6b113615c6c95a38dbea1f86985554ebd34f310
Timestamp: 1760858579 Timestamp [UCT]: 2025-10-19 07:22:59 Age [y:d:h:m:s]: 00:019:20:12:27
Block: 1393188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14194 RingCT/type: yes/0
Extra: 019df4ec23b0ae52605b23b9e8c6b113615c6c95a38dbea1f86985554ebd34f310021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a243f62f5420d2e5b55f3897ea8ad211ae2947242a27d2c3c7428b341e453bce 0.600000000000 1881447 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": 1393198, "vin": [ { "gen": { "height": 1393188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a243f62f5420d2e5b55f3897ea8ad211ae2947242a27d2c3c7428b341e453bce" } } ], "extra": [ 1, 157, 244, 236, 35, 176, 174, 82, 96, 91, 35, 185, 232, 198, 177, 19, 97, 92, 108, 149, 163, 141, 190, 161, 248, 105, 133, 85, 78, 189, 52, 243, 16, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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