Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344dd7415e6070cac2cf92002884fc798c0e77c21804fabe9f8c35bb281af323

Tx prefix hash: 4c02a1c74f836f2cc606d94aa8803cd77eb5bfaf707bdd50123c6efa35ae5b19
Tx public key: 94edfa85fc738b84e3c99686cf83bae135eb25e4b61f87a58ecfceac962fd4dd
Timestamp: 1598186616 Timestamp [UCT]: 2020-08-23 12:43:36 Age [y:d:h:m:s]: 04:131:19:01:10
Block: 129018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1058707 RingCT/type: yes/0
Extra: 0194edfa85fc738b84e3c99686cf83bae135eb25e4b61f87a58ecfceac962fd4dd02110000000a8a2ee0d9000000000000000000

1 output(s) for total of 229.367773079000 dcy

stealth address amount amount idx
00: 1d3214ece105f5ef0dd36a8487fa1c0bb6f1c432f0eac270ea0bc4f79100a623 229.367773079000 216534 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": 129028, "vin": [ { "gen": { "height": 129018 } } ], "vout": [ { "amount": 229367773079, "target": { "key": "1d3214ece105f5ef0dd36a8487fa1c0bb6f1c432f0eac270ea0bc4f79100a623" } } ], "extra": [ 1, 148, 237, 250, 133, 252, 115, 139, 132, 227, 201, 150, 134, 207, 131, 186, 225, 53, 235, 37, 228, 182, 31, 135, 165, 142, 207, 206, 172, 150, 47, 212, 221, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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