Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 922aab60ddc8e0461af8f8e6d12b2d198315bd5f987964906a730eeaeb1b9412

Tx prefix hash: 31c59d15c40d4423f41e12c342c6d71a58273378597babdf3ceb2e066b9d66ee
Tx public key: e3ca8df687adbf3a8b79c1e323bc37457fe184f781a1de5d8c5b11ab69009aa5
Timestamp: 1736618889 Timestamp [UCT]: 2025-01-11 18:08:09 Age [y:d:h:m:s]: 00:067:04:07:52
Block: 1195192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47805 RingCT/type: yes/0
Extra: 01e3ca8df687adbf3a8b79c1e323bc37457fe184f781a1de5d8c5b11ab69009aa50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c339211bccbc7568cf61e7e58babfa3ff98659e5ea5b2640768238bcddb34683 0.600000000000 1681781 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": 1195202, "vin": [ { "gen": { "height": 1195192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c339211bccbc7568cf61e7e58babfa3ff98659e5ea5b2640768238bcddb34683" } } ], "extra": [ 1, 227, 202, 141, 246, 135, 173, 191, 58, 139, 121, 193, 227, 35, 188, 55, 69, 127, 225, 132, 247, 129, 161, 222, 93, 140, 91, 17, 171, 105, 0, 154, 165, 2, 17, 0, 0, 0, 3, 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