Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e33fc854a01dca117dd3561763fc9e3ccc5549a4c0842ff65184c67c78b9e545

Tx prefix hash: 64b1f8a6d3167cb2c36d3c76c9c031ae4b85d90f7b816c19aed9ba9cc8b4e936
Tx public key: e292c0d27a9663ae962ab42cf76cf73c0bf01f17c07d42fcdf1df4c43df0cfbf
Timestamp: 1708276720 Timestamp [UCT]: 2024-02-18 17:18:40 Age [y:d:h:m:s]: 01:261:23:18:51
Block: 960364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445961 RingCT/type: yes/0
Extra: 01e292c0d27a9663ae962ab42cf76cf73c0bf01f17c07d42fcdf1df4c43df0cfbf0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8be72b9b3de9034bc8d2cf878e211652fbcc229427f1bfc91a477dff9dbdbdd0 0.600000000000 1419927 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": 960374, "vin": [ { "gen": { "height": 960364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8be72b9b3de9034bc8d2cf878e211652fbcc229427f1bfc91a477dff9dbdbdd0" } } ], "extra": [ 1, 226, 146, 192, 210, 122, 150, 99, 174, 150, 42, 180, 44, 247, 108, 247, 60, 11, 240, 31, 23, 192, 125, 66, 252, 223, 29, 244, 196, 61, 240, 207, 191, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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