Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f429fe067f8610ecbd50208bfbe2ea925a986ca97c9fe401c5e3cf81545b5f02

Tx prefix hash: 32858de50ea0a9e0f944f9b18ce1d56f8739464d9e28580d1e743582c0c507c2
Tx public key: 12b7106f70d32e3454c4bd7c709b4a79638fd51af8416f02784796b2dca0415c
Timestamp: 1702806998 Timestamp [UCT]: 2023-12-17 09:56:38 Age [y:d:h:m:s]: 01:150:15:05:21
Block: 915015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368804 RingCT/type: yes/0
Extra: 0112b7106f70d32e3454c4bd7c709b4a79638fd51af8416f02784796b2dca0415c02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4600d1fa438246ed6fc658459874f80ed665033ae5d976fb9a346db6eeaa67d9 0.600000000000 1372383 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": 915025, "vin": [ { "gen": { "height": 915015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4600d1fa438246ed6fc658459874f80ed665033ae5d976fb9a346db6eeaa67d9" } } ], "extra": [ 1, 18, 183, 16, 111, 112, 211, 46, 52, 84, 196, 189, 124, 112, 155, 74, 121, 99, 143, 213, 26, 248, 65, 111, 2, 120, 71, 150, 178, 220, 160, 65, 92, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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