Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f0e9e2c97dc5ed1a5b966c0ad4f8b2b142a215b69542113b1258807aa8112b8

Tx prefix hash: be3464de1c1314956f2cf7fb30e79e926f30f544d407a09ad4a5f27a53148fc0
Tx public key: ccb9905d4aac87748b93cee2ae13ac78017a4556e08459c68ce40489438d9495
Timestamp: 1609107648 Timestamp [UCT]: 2020-12-27 22:20:48 Age [y:d:h:m:s]: 04:063:20:28:44
Block: 170541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1058729 RingCT/type: yes/0
Extra: 01ccb9905d4aac87748b93cee2ae13ac78017a4556e08459c68ce40489438d9495021100000018aad74b3a000000000000000000

1 output(s) for total of 167.081181261000 dcy

stealth address amount amount idx
00: 96eaf6286da4c8e79d85e8ce2ab6772bbc7d33cc824e0db89c3210910e017c00 167.081181261000 319962 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": 170551, "vin": [ { "gen": { "height": 170541 } } ], "vout": [ { "amount": 167081181261, "target": { "key": "96eaf6286da4c8e79d85e8ce2ab6772bbc7d33cc824e0db89c3210910e017c00" } } ], "extra": [ 1, 204, 185, 144, 93, 74, 172, 135, 116, 139, 147, 206, 226, 174, 19, 172, 120, 1, 122, 69, 86, 224, 132, 89, 198, 140, 228, 4, 137, 67, 141, 148, 149, 2, 17, 0, 0, 0, 24, 170, 215, 75, 58, 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