Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8341e2b7fff93d7d241451dcda8ca8364cb99b6c839f52a90323e0011409815

Tx prefix hash: 5671a9501148a81a5206c8ec3b78fdb95ad662e99b9d548f858c9f84b2190be7
Tx public key: 1b020eadfd426ace36da13b34fcaa54bf75f192269f18670e012f1b96360e313
Timestamp: 1660457952 Timestamp [UCT]: 2022-08-14 06:19:12 Age [y:d:h:m:s]: 02:227:16:17:46
Block: 565477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 683938 RingCT/type: yes/0
Extra: 011b020eadfd426ace36da13b34fcaa54bf75f192269f18670e012f1b96360e313021100000001faf35c9c000000000000000000

1 output(s) for total of 8.209941601000 dcy

stealth address amount amount idx
00: 74625f7f5854723832c85ac9ea8b811d6e7a7d17e1723a2c633bbc222a1aa011 8.209941601000 998379 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": 565487, "vin": [ { "gen": { "height": 565477 } } ], "vout": [ { "amount": 8209941601, "target": { "key": "74625f7f5854723832c85ac9ea8b811d6e7a7d17e1723a2c633bbc222a1aa011" } } ], "extra": [ 1, 27, 2, 14, 173, 253, 66, 106, 206, 54, 218, 19, 179, 79, 202, 165, 75, 247, 95, 25, 34, 105, 241, 134, 112, 224, 18, 241, 185, 99, 96, 227, 19, 2, 17, 0, 0, 0, 1, 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