Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5d0c811cd2c0ef55eb7db4811b90ad162574aa25a067aa2c270bdb92c94255b

Tx prefix hash: 4c43826e4c237325a90c3a4b6d75fbf2f5a812762ff2312e43f96391e859e504
Tx public key: c9bdc1e0e9aaf6d2fe53555e321689bd7d482c8a0bbb376dc80a0c46dab133e9
Timestamp: 1672823390 Timestamp [UCT]: 2023-01-04 09:09:50 Age [y:d:h:m:s]: 01:333:11:22:22
Block: 667305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499357 RingCT/type: yes/0
Extra: 01c9bdc1e0e9aaf6d2fe53555e321689bd7d482c8a0bbb376dc80a0c46dab133e902110000000233af99f4000000000000000000

1 output(s) for total of 3.775213216000 dcy

stealth address amount amount idx
00: 6a946b55fb2fe5a31b71a094d3308573d1fcb08fe5bbf8044a5ce95f3443610d 3.775213216000 1108472 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": 667315, "vin": [ { "gen": { "height": 667305 } } ], "vout": [ { "amount": 3775213216, "target": { "key": "6a946b55fb2fe5a31b71a094d3308573d1fcb08fe5bbf8044a5ce95f3443610d" } } ], "extra": [ 1, 201, 189, 193, 224, 233, 170, 246, 210, 254, 83, 85, 94, 50, 22, 137, 189, 125, 72, 44, 138, 11, 187, 55, 109, 200, 10, 12, 70, 218, 177, 51, 233, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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