Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5ba2bb42a434009de10cf4588c38f61b4abb97f14a6900835e75b90d4175f34

Tx prefix hash: 29753f65748e07c487fa8bf6f61d0b39c8db4e2ed1f0f2a053010e5ef00df650
Tx public key: d07cd42771f2d386a76182406cbe5d4c3c44b74bc87c9d9b3a5f90f2ab8011f6
Timestamp: 1582129262 Timestamp [UCT]: 2020-02-19 16:21:02 Age [y:d:h:m:s]: 05:067:09:49:06
Block: 68292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201252 RingCT/type: yes/0
Extra: 01d07cd42771f2d386a76182406cbe5d4c3c44b74bc87c9d9b3a5f90f2ab8011f60211000000027adf42d3000000000000000000

1 output(s) for total of 364.519747546000 dcy

stealth address amount amount idx
00: 8d0f4a78729dc6adbe0d5e6cfeaba16e0c5e9874b04b8ece53d4b89d105d1df1 364.519747546000 125834 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": 68302, "vin": [ { "gen": { "height": 68292 } } ], "vout": [ { "amount": 364519747546, "target": { "key": "8d0f4a78729dc6adbe0d5e6cfeaba16e0c5e9874b04b8ece53d4b89d105d1df1" } } ], "extra": [ 1, 208, 124, 212, 39, 113, 242, 211, 134, 167, 97, 130, 64, 108, 190, 93, 76, 60, 68, 183, 75, 200, 124, 157, 155, 58, 95, 144, 242, 171, 128, 17, 246, 2, 17, 0, 0, 0, 2, 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