Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35f32a767e33414f21f668beceda2cf8abd1c09a5fbae972c001ebd104169f77

Tx prefix hash: 343b92e60de3e0a8c5b7e2d7253a589fe951ea752afc0f066704edce98b09a8d
Tx public key: 860de3381befbad087adaf73eab60a8033c1fc534bb8f925da77ec1465b5c3e5
Timestamp: 1708881324 Timestamp [UCT]: 2024-02-25 17:15:24 Age [y:d:h:m:s]: 01:079:23:35:25
Block: 965384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318198 RingCT/type: yes/0
Extra: 01860de3381befbad087adaf73eab60a8033c1fc534bb8f925da77ec1465b5c3e502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 428f382e834865a9d5ac2a41e6d9d4bdf78e87b2466427c19998790cda9fcece 0.600000000000 1425135 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": 965394, "vin": [ { "gen": { "height": 965384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "428f382e834865a9d5ac2a41e6d9d4bdf78e87b2466427c19998790cda9fcece" } } ], "extra": [ 1, 134, 13, 227, 56, 27, 239, 186, 208, 135, 173, 175, 115, 234, 182, 10, 128, 51, 193, 252, 83, 75, 184, 249, 37, 218, 119, 236, 20, 101, 181, 195, 229, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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