Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a29535e9ec6bfcb9670d2f89d8bb178336a49da0d82bf5597c0e83784dff5b8f

Tx prefix hash: 9fa0deb35129b9abfe0c8170644e979860d82c07a03f700ce3c6736dc21ff4d3
Tx public key: b2accd6b2a0f03efa16bb3ac376164cab72f99efd0b001a1b187f42f6b02f750
Timestamp: 1703676902 Timestamp [UCT]: 2023-12-27 11:35:02 Age [y:d:h:m:s]: 01:107:18:11:02
Block: 922227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338129 RingCT/type: yes/0
Extra: 01b2accd6b2a0f03efa16bb3ac376164cab72f99efd0b001a1b187f42f6b02f75002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a979674961fec54505799f0e5db3f06e8dd104f380b524cee9bab3bbfcbee1d8 0.600000000000 1379923 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": 922237, "vin": [ { "gen": { "height": 922227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a979674961fec54505799f0e5db3f06e8dd104f380b524cee9bab3bbfcbee1d8" } } ], "extra": [ 1, 178, 172, 205, 107, 42, 15, 3, 239, 161, 107, 179, 172, 55, 97, 100, 202, 183, 47, 153, 239, 208, 176, 1, 161, 177, 135, 244, 47, 107, 2, 247, 80, 2, 17, 0, 0, 0, 5, 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