Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ab65b0366941a3451b405d663d463d89749af2136749285183d5ea2420c6a8c

Tx prefix hash: 89caa0bc1c7547580e64df64a157183dab9d75a36ce30d188b4def2bba89d163
Tx public key: eeb3b70e669ab1a36d36b22ce3d5f74194100f4aed2c44eadb73a96830cf359b
Timestamp: 1617048005 Timestamp [UCT]: 2021-03-29 20:00:05 Age [y:d:h:m:s]: 04:079:03:05:15
Block: 229210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076640 RingCT/type: yes/0
Extra: 01eeb3b70e669ab1a36d36b22ce3d5f74194100f4aed2c44eadb73a96830cf359b02110000012890ec05ad000000000000000000

1 output(s) for total of 106.793540471000 dcy

stealth address amount amount idx
00: f1211e73ed4c54c002500300023a8ae4bf3242f060b20d9a263f3a89d8a0b092 106.793540471000 475550 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": 229220, "vin": [ { "gen": { "height": 229210 } } ], "vout": [ { "amount": 106793540471, "target": { "key": "f1211e73ed4c54c002500300023a8ae4bf3242f060b20d9a263f3a89d8a0b092" } } ], "extra": [ 1, 238, 179, 183, 14, 102, 154, 177, 163, 109, 54, 178, 44, 227, 213, 247, 65, 148, 16, 15, 74, 237, 44, 68, 234, 219, 115, 169, 104, 48, 207, 53, 155, 2, 17, 0, 0, 1, 40, 144, 236, 5, 173, 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