Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67ef54716f6cefcd4745829e62e13b128b95b8d11d657fdacda6a101b22f4b8e

Tx prefix hash: 4406f97a8303166de9d40c0569d919f8d2ec265393ebf2935d9a3e5d4c9e813b
Tx public key: 8022623d3aada67accf9dca4111410ebebbec0c38acfbfa12a466dc2a98c171c
Timestamp: 1699561021 Timestamp [UCT]: 2023-11-09 20:17:01 Age [y:d:h:m:s]: 01:185:00:04:11
Block: 888111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393426 RingCT/type: yes/0
Extra: 018022623d3aada67accf9dca4111410ebebbec0c38acfbfa12a466dc2a98c171c02110000000233af99f4000000000000000000

1 output(s) for total of 0.700357180000 dcy

stealth address amount amount idx
00: 1331c9d723910de1e61810ac091a512aa29931c4eac8529e981912181fc0ac61 0.700357180000 1344030 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": 888121, "vin": [ { "gen": { "height": 888111 } } ], "vout": [ { "amount": 700357180, "target": { "key": "1331c9d723910de1e61810ac091a512aa29931c4eac8529e981912181fc0ac61" } } ], "extra": [ 1, 128, 34, 98, 61, 58, 173, 166, 122, 204, 249, 220, 164, 17, 20, 16, 235, 235, 190, 192, 195, 138, 207, 191, 161, 42, 70, 109, 194, 169, 140, 23, 28, 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