Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9ab6ec177c0121f3f07eff5d9805c0bd2eba7b23d21e172ebcb3f6f8982a91c

Tx prefix hash: d1bf42d2f36231d514d474e7cc2af9419d63a5b8b638a01bc8710a31292fde97
Tx public key: df2f857f927c3a49150b9d04065e3a61202e92c5a5d22d95102f28b383f41ab6
Timestamp: 1574751465 Timestamp [UCT]: 2019-11-26 06:57:45 Age [y:d:h:m:s]: 05:001:04:18:31
Block: 17709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1143652 RingCT/type: yes/0
Extra: 01df2f857f927c3a49150b9d04065e3a61202e92c5a5d22d95102f28b383f41ab6021100000001f95225a5000000000000000000

1 output(s) for total of 536.196051843000 dcy

stealth address amount amount idx
00: a77b6f70fda5fd88efb0fde0938eded9c3caac5b26cf323e982e545f9a26dded 536.196051843000 26147 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": 17719, "vin": [ { "gen": { "height": 17709 } } ], "vout": [ { "amount": 536196051843, "target": { "key": "a77b6f70fda5fd88efb0fde0938eded9c3caac5b26cf323e982e545f9a26dded" } } ], "extra": [ 1, 223, 47, 133, 127, 146, 124, 58, 73, 21, 11, 157, 4, 6, 94, 58, 97, 32, 46, 146, 197, 165, 210, 45, 149, 16, 47, 40, 179, 131, 244, 26, 182, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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