Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4f35f7e007f043163111a95a7ef6338b6f5fc931c3b83518edfdf786fc27830

Tx prefix hash: 1325b17aa3090f75651bb976a60b868db4251d0a8cfefef7bfeacebff1e94641
Tx public key: 8f51914b9a92e033ba9a1567ad9aa558183ada79c4cf7a2b83330e109669c35f
Timestamp: 1731626403 Timestamp [UCT]: 2024-11-14 23:20:03 Age [y:d:h:m:s]: 01:004:14:48:30
Block: 1153854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261717 RingCT/type: yes/0
Extra: 018f51914b9a92e033ba9a1567ad9aa558183ada79c4cf7a2b83330e109669c35f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ae1f64fe6a9421463078d7b2d36d15df7c9914da67e30c4109e4a8c990eecae 0.600000000000 1639465 of 15

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": 1153864, "vin": [ { "gen": { "height": 1153854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ae1f64fe6a9421463078d7b2d36d15df7c9914da67e30c4109e4a8c990eecae" } } ], "extra": [ 1, 143, 81, 145, 75, 154, 146, 224, 51, 186, 154, 21, 103, 173, 154, 165, 88, 24, 58, 218, 121, 196, 207, 122, 43, 131, 51, 14, 16, 150, 105, 195, 95, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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