Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6421966959c493f208f5042470ffcbfef80e9518384da583b167e98e1737ee67

Tx prefix hash: 2c0c7fa57c6c849af5ffacc8d515e12d0a93db1d51236c63bec59d8728c779fc
Tx public key: a069d983e452b0a8ee0704f5dbaf5d889ae2ddefa59e88e93b687d7b242c1ea9
Timestamp: 1582986453 Timestamp [UCT]: 2020-02-29 14:27:33 Age [y:d:h:m:s]: 05:095:02:48:13
Block: 74193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1222284 RingCT/type: yes/0
Extra: 01a069d983e452b0a8ee0704f5dbaf5d889ae2ddefa59e88e93b687d7b242c1ea902110000019c12c4732d000000000000000000

1 output(s) for total of 348.478583712000 dcy

stealth address amount amount idx
00: 021c106a79a9b6143f1ff1cbaf05e5cea0b6fca267e802a64894f5b68b7e953d 348.478583712000 137152 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": 74203, "vin": [ { "gen": { "height": 74193 } } ], "vout": [ { "amount": 348478583712, "target": { "key": "021c106a79a9b6143f1ff1cbaf05e5cea0b6fca267e802a64894f5b68b7e953d" } } ], "extra": [ 1, 160, 105, 217, 131, 228, 82, 176, 168, 238, 7, 4, 245, 219, 175, 93, 136, 154, 226, 221, 239, 165, 158, 136, 233, 59, 104, 125, 123, 36, 44, 30, 169, 2, 17, 0, 0, 1, 156, 18, 196, 115, 45, 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