Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eadf4c2240fbea78bdbc8663aa5c1cdb4dfeaf3a52ebfc796c8359f4736a334

Tx prefix hash: 0fa1dedeb1cf13514ce0d58cb7cecacc2168c593958272af5d9bc358fedcf093
Tx public key: 3d0a4164519e5f1a744a087496b66f810b2759cb06ad5758bfe4ca0e4c9f8853
Timestamp: 1702689570 Timestamp [UCT]: 2023-12-16 01:19:30 Age [y:d:h:m:s]: 01:124:07:14:38
Block: 914044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349981 RingCT/type: yes/0
Extra: 013d0a4164519e5f1a744a087496b66f810b2759cb06ad5758bfe4ca0e4c9f885302110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f1a232e51098143a3503bcfbbe3e9d20763a0d563c983bbb43e05fc185a21d4 0.600000000000 1371326 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": 914054, "vin": [ { "gen": { "height": 914044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f1a232e51098143a3503bcfbbe3e9d20763a0d563c983bbb43e05fc185a21d4" } } ], "extra": [ 1, 61, 10, 65, 100, 81, 158, 95, 26, 116, 74, 8, 116, 150, 182, 111, 129, 11, 39, 89, 203, 6, 173, 87, 88, 191, 228, 202, 14, 76, 159, 136, 83, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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