Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ad1dabfc04d79c5ebec7f9242583291aa7c87df7f0cda72c80f8b2721353fc8

Tx prefix hash: 13874c5828b0d2f188e5fcdc857515e0817e9a9d6910068749e7cc2d35f61253
Tx public key: 97b8a7d74dee0e6d68b661027774ea70f424da68b53ad48cf8c519717c1ea91e
Timestamp: 1674245982 Timestamp [UCT]: 2023-01-20 20:19:42 Age [y:d:h:m:s]: 02:000:15:04:00
Block: 679106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522278 RingCT/type: yes/0
Extra: 0197b8a7d74dee0e6d68b661027774ea70f424da68b53ad48cf8c519717c1ea91e021100000002faf35c9c000000000000000000

1 output(s) for total of 3.450164924000 dcy

stealth address amount amount idx
00: d39934e6b76a29d68ca9d5e6ddf905d9125fa62a1ac7f1942022a336c9b9e553 3.450164924000 1121067 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": 679116, "vin": [ { "gen": { "height": 679106 } } ], "vout": [ { "amount": 3450164924, "target": { "key": "d39934e6b76a29d68ca9d5e6ddf905d9125fa62a1ac7f1942022a336c9b9e553" } } ], "extra": [ 1, 151, 184, 167, 215, 77, 238, 14, 109, 104, 182, 97, 2, 119, 116, 234, 112, 244, 36, 218, 104, 181, 58, 212, 140, 248, 197, 25, 113, 124, 30, 169, 30, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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