Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e911f72ab65a99f822776591d580dbb1bab3892701908d471042d8a72bb961a0

Tx prefix hash: 9ad8c1f3132bd2acb0e8d1dcdd807df5493e5d9655c3f1e92d7a2ea2a51f3bfe
Tx public key: a4d25824b2b3ff45f848c5a16af2bdf35f1f6cae0625bafdf9a98c84a18a8907
Timestamp: 1638042677 Timestamp [UCT]: 2021-11-27 19:51:17 Age [y:d:h:m:s]: 03:342:10:24:25
Block: 383456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1021144 RingCT/type: yes/0
Extra: 01a4d25824b2b3ff45f848c5a16af2bdf35f1f6cae0625bafdf9a98c84a18a890702110000000537cb3088000000000000000000

1 output(s) for total of 32.919366382000 dcy

stealth address amount amount idx
00: aff0e8b8552fdb0527af1e2391c7a9fa9aed9d39f390282869a293740067a828 32.919366382000 774165 of 0

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": 383466, "vin": [ { "gen": { "height": 383456 } } ], "vout": [ { "amount": 32919366382, "target": { "key": "aff0e8b8552fdb0527af1e2391c7a9fa9aed9d39f390282869a293740067a828" } } ], "extra": [ 1, 164, 210, 88, 36, 178, 179, 255, 69, 248, 72, 197, 161, 106, 242, 189, 243, 95, 31, 108, 174, 6, 37, 186, 253, 249, 169, 140, 132, 161, 138, 137, 7, 2, 17, 0, 0, 0, 5, 55, 203, 48, 136, 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