Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d29eaadb1bbf607ccfe7cc8d581dc42bea1e5e691010e511270894c92c963327

Tx prefix hash: d8d771548cbc7638264bf8a6b13031da8388556977d5263a9c872b64f0c43e6e
Tx public key: 3726432a9f2b3584c5920afb3ec22282dcd9d8640274fca1dd4a37b2f4d5d54b
Timestamp: 1686055603 Timestamp [UCT]: 2023-06-06 12:46:43 Age [y:d:h:m:s]: 02:125:06:57:57
Block: 776387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609272 RingCT/type: yes/0
Extra: 013726432a9f2b3584c5920afb3ec22282dcd9d8640274fca1dd4a37b2f4d5d54b02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.642508932000 dcy

stealth address amount amount idx
00: 0a5e5b1a8f6a36f2ce305dbc45eda0ec899c32149898096079187a45275b1541 1.642508932000 1225932 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": 776397, "vin": [ { "gen": { "height": 776387 } } ], "vout": [ { "amount": 1642508932, "target": { "key": "0a5e5b1a8f6a36f2ce305dbc45eda0ec899c32149898096079187a45275b1541" } } ], "extra": [ 1, 55, 38, 67, 42, 159, 43, 53, 132, 197, 146, 10, 251, 62, 194, 34, 130, 220, 217, 216, 100, 2, 116, 252, 161, 221, 74, 55, 178, 244, 213, 213, 75, 2, 17, 0, 0, 0, 3, 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