Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56c7ed3c0c5672385b03d2a008cca1150fc3c3802dec53cfd35a02b3b89a8e38

Tx prefix hash: a3dbb8758af400be229afb4134ca6af6edd164483be88e028264b781e3aeef02
Tx public key: 968ed9e7b5a9fcc0ecfd308bc9237f5ce883f8c3e69480d3625b14fe49cfbc70
Timestamp: 1694061032 Timestamp [UCT]: 2023-09-07 04:30:32 Age [y:d:h:m:s]: 01:258:04:41:34
Block: 842690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445676 RingCT/type: yes/0
Extra: 01968ed9e7b5a9fcc0ecfd308bc9237f5ce883f8c3e69480d3625b14fe49cfbc700211000000034b8f5122000000000000000000

1 output(s) for total of 0.990417442000 dcy

stealth address amount amount idx
00: 338061066cc27b5637692dec6bf573a9cdd0c3afb92c61b2bba0d3f66b900834 0.990417442000 1295834 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": 842700, "vin": [ { "gen": { "height": 842690 } } ], "vout": [ { "amount": 990417442, "target": { "key": "338061066cc27b5637692dec6bf573a9cdd0c3afb92c61b2bba0d3f66b900834" } } ], "extra": [ 1, 150, 142, 217, 231, 181, 169, 252, 192, 236, 253, 48, 139, 201, 35, 127, 92, 232, 131, 248, 195, 230, 148, 128, 211, 98, 91, 20, 254, 73, 207, 188, 112, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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