Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8366e103d3dbdbf05326d10bc9b4dd37acbd473ed5791255dba9cc9f6edb70e7

Tx prefix hash: 3bb316ffc0b1b280267a7e88e8614a3d8cb2bd14e25221bd32d9f41034fd860e
Tx public key: 345709f336a242c09bb966c48350dfdc4e539868accbc4ba3dcebe529d8de85a
Timestamp: 1722586898 Timestamp [UCT]: 2024-08-02 08:21:38 Age [y:d:h:m:s]: 01:095:18:38:11
Block: 1078997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326921 RingCT/type: yes/0
Extra: 01345709f336a242c09bb966c48350dfdc4e539868accbc4ba3dcebe529d8de85a02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9f84965f2a186c06c7e0569715486381c421508e103951f6f0613302c4672a8 0.600000000000 1551764 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": 1079007, "vin": [ { "gen": { "height": 1078997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9f84965f2a186c06c7e0569715486381c421508e103951f6f0613302c4672a8" } } ], "extra": [ 1, 52, 87, 9, 243, 54, 162, 66, 192, 155, 185, 102, 196, 131, 80, 223, 220, 78, 83, 152, 104, 172, 203, 196, 186, 61, 206, 190, 82, 157, 141, 232, 90, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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