Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5725ba65b60ddef266871fafa85236dd868c8f93c76ed16c794472555e5ae7d

Tx prefix hash: 2e812568532f9358da153fd3421cf448db9fd3d48155b9e9697613e4298be3c9
Tx public key: a24badd0b90db83bf626a1ba992433a692dc4a0786d9fc2bddfc9a6f61ad7fac
Timestamp: 1724042005 Timestamp [UCT]: 2024-08-19 04:33:25 Age [y:d:h:m:s]: 00:225:22:31:54
Block: 1091075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161322 RingCT/type: yes/0
Extra: 01a24badd0b90db83bf626a1ba992433a692dc4a0786d9fc2bddfc9a6f61ad7fac021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8c0a42a9ad4ba0a9d909d181f9914530cbfc9934d55fa90eaae3ac97887f26c 0.600000000000 1565700 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": 1091085, "vin": [ { "gen": { "height": 1091075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8c0a42a9ad4ba0a9d909d181f9914530cbfc9934d55fa90eaae3ac97887f26c" } } ], "extra": [ 1, 162, 75, 173, 208, 185, 13, 184, 59, 246, 38, 161, 186, 153, 36, 51, 166, 146, 220, 74, 7, 134, 217, 252, 43, 221, 252, 154, 111, 97, 173, 127, 172, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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