Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4f755781992ec8310c74b0df10d96598d3233d353ade5bf7ce3e6415e1a8c11

Tx prefix hash: 64495d318c45a5e6868eb632ec02d78e3877809b19d781b8677a6dfde31bf6ce
Tx public key: e166a9351958790dae1f2a9ed4cbe6019dc30325ac9e5122f0378ccc847e352e
Timestamp: 1698330155 Timestamp [UCT]: 2023-10-26 14:22:35 Age [y:d:h:m:s]: 01:087:11:17:48
Block: 878120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323694 RingCT/type: yes/0
Extra: 01e166a9351958790dae1f2a9ed4cbe6019dc30325ac9e5122f0378ccc847e352e0211000000074b8f5122000000000000000000

1 output(s) for total of 0.755829660000 dcy

stealth address amount amount idx
00: b8b9147e8a511d89f56f662b5a6f950d4838476205a3ef8090620e2ef5cc6cca 0.755829660000 1333534 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": 878130, "vin": [ { "gen": { "height": 878120 } } ], "vout": [ { "amount": 755829660, "target": { "key": "b8b9147e8a511d89f56f662b5a6f950d4838476205a3ef8090620e2ef5cc6cca" } } ], "extra": [ 1, 225, 102, 169, 53, 25, 88, 121, 13, 174, 31, 42, 158, 212, 203, 230, 1, 157, 195, 3, 37, 172, 158, 81, 34, 240, 55, 140, 204, 132, 126, 53, 46, 2, 17, 0, 0, 0, 7, 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