Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f245e8458ea5f5fbeb7c605f695719a3eed37bd05b7d908b5587ff7ecc6f0bad

Tx prefix hash: 5a04b0a37a85a18aeeb35801ee82e341d0aea509d3810dc6cf5a11838dd09ac6
Tx public key: 7549532176937ca4a8e651e9e6e97031f008e296c72e000743a1b832090593a1
Timestamp: 1592759689 Timestamp [UCT]: 2020-06-21 17:14:49 Age [y:d:h:m:s]: 04:189:16:10:09
Block: 109918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074277 RingCT/type: yes/0
Extra: 017549532176937ca4a8e651e9e6e97031f008e296c72e000743a1b832090593a102110000002846a11e8a000000000000000000

1 output(s) for total of 265.336371014000 dcy

stealth address amount amount idx
00: 9409789335efd2ffcedb4ff7fc2eff7c07227567f7fc54415bf852fa05e426d8 265.336371014000 190522 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": 109928, "vin": [ { "gen": { "height": 109918 } } ], "vout": [ { "amount": 265336371014, "target": { "key": "9409789335efd2ffcedb4ff7fc2eff7c07227567f7fc54415bf852fa05e426d8" } } ], "extra": [ 1, 117, 73, 83, 33, 118, 147, 124, 164, 168, 230, 81, 233, 230, 233, 112, 49, 240, 8, 226, 150, 199, 46, 0, 7, 67, 161, 184, 50, 9, 5, 147, 161, 2, 17, 0, 0, 0, 40, 70, 161, 30, 138, 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