Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9c48e8e015e5e216a79cc5307d430fbc8b6385649cdaa5c1506a382f3362fd8

Tx prefix hash: 52afb70e33369a60c5df370e9fbc4e05e03cfb4e428d3683fcac15415f9aded9
Tx public key: ff6e1e446b3087824bbb80f418dae27186dc7e39b1c4b4bc470d74536efe8fd3
Timestamp: 1702848876 Timestamp [UCT]: 2023-12-17 21:34:36 Age [y:d:h:m:s]: 01:112:22:17:00
Block: 915363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341833 RingCT/type: yes/0
Extra: 01ff6e1e446b3087824bbb80f418dae27186dc7e39b1c4b4bc470d74536efe8fd302110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5ec7ff6ef9629cb04bf83c44b5d0f97bbce762f10741e0564cfa262c8b16c55 0.600000000000 1372759 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": 915373, "vin": [ { "gen": { "height": 915363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5ec7ff6ef9629cb04bf83c44b5d0f97bbce762f10741e0564cfa262c8b16c55" } } ], "extra": [ 1, 255, 110, 30, 68, 107, 48, 135, 130, 75, 187, 128, 244, 24, 218, 226, 113, 134, 220, 126, 57, 177, 196, 180, 188, 71, 13, 116, 83, 110, 254, 143, 211, 2, 17, 0, 0, 0, 8, 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