Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee79709832da7bfb2424e5b7efab2a58dcf5b69e5502aefd118b05c818b5039b

Tx prefix hash: af3a62b2ee7d919708221b73fe9f0dfea8bd17dcca00b8641c9d43125d747493
Tx public key: 80ec0d05daa1a00ade6a9ebe237408e557d83137d14b9c9d06c5b331a1288eae
Timestamp: 1755203326 Timestamp [UCT]: 2025-08-14 20:28:46 Age [y:d:h:m:s]: 00:046:23:08:47
Block: 1346800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33122 RingCT/type: yes/0
Extra: 0180ec0d05daa1a00ade6a9ebe237408e557d83137d14b9c9d06c5b331a1288eae021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 888abb7659e7be25c311ed729f0b20fe57581e5ad95c54d2bc0a776408b5d368 0.600000000000 1834705 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": 1346810, "vin": [ { "gen": { "height": 1346800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "888abb7659e7be25c311ed729f0b20fe57581e5ad95c54d2bc0a776408b5d368" } } ], "extra": [ 1, 128, 236, 13, 5, 218, 161, 160, 10, 222, 106, 158, 190, 35, 116, 8, 229, 87, 216, 49, 55, 209, 75, 156, 157, 6, 197, 179, 49, 161, 40, 142, 174, 2, 17, 0, 0, 0, 4, 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