Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9995545332e898fdefc0c6e5c95ed155496a0b9fc023d9ffbde2bac172cb3c8

Tx prefix hash: d3206bd2a361f52ebd9fe14c648bd24da48c9eb5ddd4f65f0097f27531bce7ab
Tx public key: 4aa5a2264255520991c7a55fd3d914888e7233575378d58e2b6bdec1bcd64cbe
Timestamp: 1680969618 Timestamp [UCT]: 2023-04-08 16:00:18 Age [y:d:h:m:s]: 01:321:21:39:40
Block: 734290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491238 RingCT/type: yes/0
Extra: 014aa5a2264255520991c7a55fd3d914888e7233575378d58e2b6bdec1bcd64cbe0211000000025029cbac000000000000000000

1 output(s) for total of 2.264605918000 dcy

stealth address amount amount idx
00: fa034c8b5928dfc9d002ad1e0c12da1e405fdc2a1748581db802031114a8dbb1 2.264605918000 1180471 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": 734300, "vin": [ { "gen": { "height": 734290 } } ], "vout": [ { "amount": 2264605918, "target": { "key": "fa034c8b5928dfc9d002ad1e0c12da1e405fdc2a1748581db802031114a8dbb1" } } ], "extra": [ 1, 74, 165, 162, 38, 66, 85, 82, 9, 145, 199, 165, 95, 211, 217, 20, 136, 142, 114, 51, 87, 83, 120, 213, 142, 43, 107, 222, 193, 188, 214, 76, 190, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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