Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ecac34e49285dad848edec0d47b1ba1509f4f5316c879d6269b1813c084d160

Tx prefix hash: c6acc034f373c68f122cee905a9da24dd004e4a931fcbb084306942694dc01c9
Tx public key: 570205c933bf3adad0d5e837dff63dd9dcb9fe6093d8afdb476a67463882e761
Timestamp: 1581560550 Timestamp [UCT]: 2020-02-13 02:22:30 Age [y:d:h:m:s]: 04:362:19:34:07
Block: 63789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151287 RingCT/type: yes/0
Extra: 01570205c933bf3adad0d5e837dff63dd9dcb9fe6093d8afdb476a67463882e761021100000009c9f743ef000000000000000000

1 output(s) for total of 377.260534493000 dcy

stealth address amount amount idx
00: 234ebd3bbd1f5be4095d6a6e66b32a082e0f6914a9a5b0f250fc256605528651 377.260534493000 117601 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": 63799, "vin": [ { "gen": { "height": 63789 } } ], "vout": [ { "amount": 377260534493, "target": { "key": "234ebd3bbd1f5be4095d6a6e66b32a082e0f6914a9a5b0f250fc256605528651" } } ], "extra": [ 1, 87, 2, 5, 201, 51, 191, 58, 218, 208, 213, 232, 55, 223, 246, 61, 217, 220, 185, 254, 96, 147, 216, 175, 219, 71, 106, 103, 70, 56, 130, 231, 97, 2, 17, 0, 0, 0, 9, 201, 247, 67, 239, 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