Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9b77aae00157831f4e689e6e6e5f4c7dbd490bd354ba567fcce9ba5506a07d7

Tx prefix hash: 23e5a1b41eb6df01fbea35ac274a41fdec6132c0e13dd7f2ead3e70c82c826b7
Tx public key: 0dedf95bc1f81814f45d0ffc9793acce32dca038b824fa7bfaafd6db3cb790f6
Timestamp: 1581475967 Timestamp [UCT]: 2020-02-12 02:52:47 Age [y:d:h:m:s]: 04:221:13:07:19
Block: 63241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1050370 RingCT/type: yes/0
Extra: 010dedf95bc1f81814f45d0ffc9793acce32dca038b824fa7bfaafd6db3cb790f60211000000147adf42d3000000000000000000

1 output(s) for total of 378.858094054000 dcy

stealth address amount amount idx
00: 15b9cfb73895d7eb0ed8e50efd3bcfd8bb8836e6587784acf84440a106b54022 378.858094054000 116576 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": 63251, "vin": [ { "gen": { "height": 63241 } } ], "vout": [ { "amount": 378858094054, "target": { "key": "15b9cfb73895d7eb0ed8e50efd3bcfd8bb8836e6587784acf84440a106b54022" } } ], "extra": [ 1, 13, 237, 249, 91, 193, 248, 24, 20, 244, 93, 15, 252, 151, 147, 172, 206, 50, 220, 160, 56, 184, 36, 250, 123, 250, 175, 214, 219, 60, 183, 144, 246, 2, 17, 0, 0, 0, 20, 122, 223, 66, 211, 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