Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7fef29ffc06d1350642eba9e0648faed3596680878a3739d1aca3ad9ea149f6

Tx prefix hash: d444d0a8c336b00755896dd5fdc7f7157562e845988a92cb1c5e113c242e60d6
Tx public key: 9e1b2d6fba2cbbe4c2908435601b57ef64e378970dd8bc4a0fd5370a24012617
Timestamp: 1704998840 Timestamp [UCT]: 2024-01-11 18:47:20 Age [y:d:h:m:s]: 01:096:03:20:26
Block: 933175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329821 RingCT/type: yes/0
Extra: 019e1b2d6fba2cbbe4c2908435601b57ef64e378970dd8bc4a0fd5370a2401261702110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8aa9cc5a4a3cec72361f3fe33097a042441b4b6c09cfd8cce067aae199eb6562 0.600000000000 1391133 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": 933185, "vin": [ { "gen": { "height": 933175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aa9cc5a4a3cec72361f3fe33097a042441b4b6c09cfd8cce067aae199eb6562" } } ], "extra": [ 1, 158, 27, 45, 111, 186, 44, 187, 228, 194, 144, 132, 53, 96, 27, 87, 239, 100, 227, 120, 151, 13, 216, 188, 74, 15, 213, 55, 10, 36, 1, 38, 23, 2, 17, 0, 0, 0, 14, 122, 156, 244, 199, 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