Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06a50c1c1849bdc1e63791a2aac4dd1a78c84d17948d05c3bf9a2a0699ba0e2a

Tx prefix hash: 577aa94986b9c78de1d3b6802c470279ea109d38b601c3105bcf3a6887964583
Tx public key: 0a7fcc4f275d9fb78b518bf1af17a38fb4a31c8da80392aad5a22d27b9aa329e
Timestamp: 1645393870 Timestamp [UCT]: 2022-02-20 21:51:10 Age [y:d:h:m:s]: 02:352:12:52:38
Block: 442903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 771126 RingCT/type: yes/0
Extra: 010a7fcc4f275d9fb78b518bf1af17a38fb4a31c8da80392aad5a22d27b9aa329e021100000005d3fcec30000000000000000000

1 output(s) for total of 20.916007669000 dcy

stealth address amount amount idx
00: 9efb74765a87a24666eecda11c62fe1d01a7a4004004fca9b2bc90dd3dcfedd3 20.916007669000 855798 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": 442913, "vin": [ { "gen": { "height": 442903 } } ], "vout": [ { "amount": 20916007669, "target": { "key": "9efb74765a87a24666eecda11c62fe1d01a7a4004004fca9b2bc90dd3dcfedd3" } } ], "extra": [ 1, 10, 127, 204, 79, 39, 93, 159, 183, 139, 81, 139, 241, 175, 23, 163, 143, 180, 163, 28, 141, 168, 3, 146, 170, 213, 162, 45, 39, 185, 170, 50, 158, 2, 17, 0, 0, 0, 5, 211, 252, 236, 48, 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