Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0c65fa71eedf81235e189809ecd408cc8ddf1deac9f2587d92d9f80eb5e753d

Tx prefix hash: d01f2087dd47782e621079bfbd76d62e98ff9b90be47f1f746a5292f65e89993
Tx public key: c88fb91c5ad8c16223c38eec73201b63f2fc00eb6e53d36cc384282c62969caa
Timestamp: 1578478524 Timestamp [UCT]: 2020-01-08 10:15:24 Age [y:d:h:m:s]: 04:357:06:25:10
Block: 41130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144713 RingCT/type: yes/0
Extra: 01c88fb91c5ad8c16223c38eec73201b63f2fc00eb6e53d36cc384282c62969caa0211000000234943cd9f000000000000000000

1 output(s) for total of 448.456251113000 dcy

stealth address amount amount idx
00: 84882e940b351812e5b5205465770add6b71e5de5338078c29d47d2e7f0bf9b8 448.456251113000 72979 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": 41140, "vin": [ { "gen": { "height": 41130 } } ], "vout": [ { "amount": 448456251113, "target": { "key": "84882e940b351812e5b5205465770add6b71e5de5338078c29d47d2e7f0bf9b8" } } ], "extra": [ 1, 200, 143, 185, 28, 90, 216, 193, 98, 35, 195, 142, 236, 115, 32, 27, 99, 242, 252, 0, 235, 110, 83, 211, 108, 195, 132, 40, 44, 98, 150, 156, 170, 2, 17, 0, 0, 0, 35, 73, 67, 205, 159, 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