Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9136f985deca8450f6f5fd595dc4bd0c0ead5700c134e11c31ffad57a309ac90

Tx prefix hash: 5cb126d513c6ff4d114c07445e3028683d8daf8a4ed180ee9d72523dd1339e08
Tx public key: f275c4b4130fb1b205eb91fdd152f875061cb72d8c873bb61648802cd70ed236
Timestamp: 1593018084 Timestamp [UCT]: 2020-06-24 17:01:24 Age [y:d:h:m:s]: 04:297:18:37:22
Block: 110520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152875 RingCT/type: yes/0
Extra: 01f275c4b4130fb1b205eb91fdd152f875061cb72d8c873bb61648802cd70ed23602110000002946a11e8a000000000000000000

1 output(s) for total of 264.120498474000 dcy

stealth address amount amount idx
00: 0d4b5bc931a33e83456e2c6c4de37253d615cf94e623d50c19132a77cd001132 264.120498474000 191406 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": 110530, "vin": [ { "gen": { "height": 110520 } } ], "vout": [ { "amount": 264120498474, "target": { "key": "0d4b5bc931a33e83456e2c6c4de37253d615cf94e623d50c19132a77cd001132" } } ], "extra": [ 1, 242, 117, 196, 180, 19, 15, 177, 178, 5, 235, 145, 253, 209, 82, 248, 117, 6, 28, 183, 45, 140, 135, 59, 182, 22, 72, 128, 44, 215, 14, 210, 54, 2, 17, 0, 0, 0, 41, 70, 161, 30, 138, 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