Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ffd3c8f3a9b3bd8a25516bae7839179797c3ea642a7bf01bc47647909c215db

Tx prefix hash: d5fbb7c28852cf17dd7f7dc3d554a7a78162abd7d55c6d5a5ff0e9f19636433e
Tx public key: a57a6d10b8f41e5cb2511fcb11d303e14f1254530b8529e60113d248d3c2c400
Timestamp: 1578945549 Timestamp [UCT]: 2020-01-13 19:59:09 Age [y:d:h:m:s]: 05:296:17:39:04
Block: 44932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1359888 RingCT/type: yes/0
Extra: 01a57a6d10b8f41e5cb2511fcb11d303e14f1254530b8529e60113d248d3c2c4000211000000064ac5aa02000000000000000000

1 output(s) for total of 435.642226559000 dcy

stealth address amount amount idx
00: 8d24af683c1270b272dc26665f5b90e0ddc0015e9a5b34db514ed86a5493068c 435.642226559000 81934 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": 44942, "vin": [ { "gen": { "height": 44932 } } ], "vout": [ { "amount": 435642226559, "target": { "key": "8d24af683c1270b272dc26665f5b90e0ddc0015e9a5b34db514ed86a5493068c" } } ], "extra": [ 1, 165, 122, 109, 16, 184, 244, 30, 92, 178, 81, 31, 203, 17, 211, 3, 225, 79, 18, 84, 83, 11, 133, 41, 230, 1, 19, 210, 72, 211, 194, 196, 0, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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