Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99075879a4523e9caafd47c7abe8f673dbee671fe2401005ff075cd8d50cda9e

Tx prefix hash: 7e3d057dd95adc550f8aba6f1261d00d376f1f18866da581288f37d6e12874f2
Tx public key: e8e1b45bfc1abed57736af16d76965f03535ac39835b6f16ba8d997cb0dee2b6
Timestamp: 1704505095 Timestamp [UCT]: 2024-01-06 01:38:15 Age [y:d:h:m:s]: 01:312:22:20:00
Block: 929066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482511 RingCT/type: yes/0
Extra: 01e8e1b45bfc1abed57736af16d76965f03535ac39835b6f16ba8d997cb0dee2b60211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 329cc0bdf54b27651ccf933889cbf6cd8d5a82ea326636d27a0a41fb48623a7d 0.600000000000 1386934 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": 929076, "vin": [ { "gen": { "height": 929066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "329cc0bdf54b27651ccf933889cbf6cd8d5a82ea326636d27a0a41fb48623a7d" } } ], "extra": [ 1, 232, 225, 180, 91, 252, 26, 190, 213, 119, 54, 175, 22, 215, 105, 101, 240, 53, 53, 172, 57, 131, 91, 111, 22, 186, 141, 153, 124, 176, 222, 226, 182, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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