Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da3d3bcb6bb2c63cd7a73e3edf9f8011f611be50f097603c6dd6cb0ab39c84ff

Tx prefix hash: 39179c3332eebc4836b08455e7bf3bc03765abe6b2acfd8499ef410f27397ce5
Tx public key: f32572945fc45361a15ccdb70229dd665aa1add3fcbc103627a33b2eb5bc6ea5
Timestamp: 1634591647 Timestamp [UCT]: 2021-10-18 21:14:07 Age [y:d:h:m:s]: 03:073:22:29:40
Block: 355764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 830887 RingCT/type: yes/0
Extra: 01f32572945fc45361a15ccdb70229dd665aa1add3fcbc103627a33b2eb5bc6ea502110000001a5410958b000000000000000000

1 output(s) for total of 40.663672456000 dcy

stealth address amount amount idx
00: c136cb31e6117bc7ed8a099d806d50f211166d94b23ba4576caf9f9d6f986251 40.663672456000 726180 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": 355774, "vin": [ { "gen": { "height": 355764 } } ], "vout": [ { "amount": 40663672456, "target": { "key": "c136cb31e6117bc7ed8a099d806d50f211166d94b23ba4576caf9f9d6f986251" } } ], "extra": [ 1, 243, 37, 114, 148, 95, 196, 83, 97, 161, 92, 205, 183, 2, 41, 221, 102, 90, 161, 173, 211, 252, 188, 16, 54, 39, 163, 59, 46, 181, 188, 110, 165, 2, 17, 0, 0, 0, 26, 84, 16, 149, 139, 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