Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50784f1ff23681c10db2dda090a886a83c9dcb13ee00cc52c7ae3c31f6e0fb54

Tx prefix hash: 667fe572a650c63919ca0c1faebdca73880cb8d035cf3d3475d2259283a848ab
Tx public key: 538e42fcdd0d1c2b90df9cbfe4d6c3eb5d5736c36dc6118e50f4eb0c5fb5f501
Timestamp: 1708638800 Timestamp [UCT]: 2024-02-22 21:53:20 Age [y:d:h:m:s]: 01:092:02:41:56
Block: 963364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326899 RingCT/type: yes/0
Extra: 01538e42fcdd0d1c2b90df9cbfe4d6c3eb5d5736c36dc6118e50f4eb0c5fb5f50102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58a7916e31a6a6bc439d5eda1f24e98faf131452aecf48c9a3fee9a4a4e73517 0.600000000000 1423067 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": 963374, "vin": [ { "gen": { "height": 963364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58a7916e31a6a6bc439d5eda1f24e98faf131452aecf48c9a3fee9a4a4e73517" } } ], "extra": [ 1, 83, 142, 66, 252, 221, 13, 28, 43, 144, 223, 156, 191, 228, 214, 195, 235, 93, 87, 54, 195, 109, 198, 17, 142, 80, 244, 235, 12, 95, 181, 245, 1, 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