Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9a0c45231eba894bcdd3e189a77b3855217d288bb2be8f8e62cd421826e9d2c

Tx prefix hash: 4dc5ad357a2a0ae20eb5d75cc96605d6ee19f145da4e774af05de7de1392eeb8
Tx public key: bd8a5f5377e876a5e4022218340e559dd121bf1af5528b98deaea68b84e17fc8
Timestamp: 1741654058 Timestamp [UCT]: 2025-03-11 00:47:38 Age [y:d:h:m:s]: 00:297:08:12:00
Block: 1236622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210301 RingCT/type: yes/0
Extra: 01bd8a5f5377e876a5e4022218340e559dd121bf1af5528b98deaea68b84e17fc80211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d2140f11c5029c9d8f51c295a411cbce3c9e513a63e69a07b94ecc9dc54f2ae 0.600000000000 1723569 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": 1236632, "vin": [ { "gen": { "height": 1236622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d2140f11c5029c9d8f51c295a411cbce3c9e513a63e69a07b94ecc9dc54f2ae" } } ], "extra": [ 1, 189, 138, 95, 83, 119, 232, 118, 165, 228, 2, 34, 24, 52, 14, 85, 157, 209, 33, 191, 26, 245, 82, 139, 152, 222, 174, 166, 139, 132, 225, 127, 200, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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