Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6afefd49c80fadac0bab15cf49d630389debbd48dfd1fbae58148411a1a34158

Tx prefix hash: 5e8e83389bfa25c224d4b1bc373a1827f97166804cd03e6894482110656f9820
Tx public key: 7decff110a6af3263e36eae521bc3d1c48b304caa4480a3ffb732cdcc1ecbfc3
Timestamp: 1581892907 Timestamp [UCT]: 2020-02-16 22:41:47 Age [y:d:h:m:s]: 04:355:17:18:11
Block: 66282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146463 RingCT/type: yes/0
Extra: 017decff110a6af3263e36eae521bc3d1c48b304caa4480a3ffb732cdcc1ecbfc3021100000015d81c26c0000000000000000000

1 output(s) for total of 370.159180823000 dcy

stealth address amount amount idx
00: 435ba9b14b5f36dc1a025209f53cab2996a844753e96634ccc9d86c3b3c65bd9 370.159180823000 122147 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": 66292, "vin": [ { "gen": { "height": 66282 } } ], "vout": [ { "amount": 370159180823, "target": { "key": "435ba9b14b5f36dc1a025209f53cab2996a844753e96634ccc9d86c3b3c65bd9" } } ], "extra": [ 1, 125, 236, 255, 17, 10, 106, 243, 38, 62, 54, 234, 229, 33, 188, 61, 28, 72, 179, 4, 202, 164, 72, 10, 63, 251, 115, 44, 220, 193, 236, 191, 195, 2, 17, 0, 0, 0, 21, 216, 28, 38, 192, 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