Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a6a0ca03c72e3b3ab042024c2f9b7843091cf7dcf6f8eed235fc102e9adb844

Tx prefix hash: d338144d67392cb1c19abc4d58defba1a692170ae0465b3c277fa75a98f41ac6
Tx public key: ad7af26c93dee5ee1453387d81c386cb9062f0139658509e7a1ac4edbb315a05
Timestamp: 1731171311 Timestamp [UCT]: 2024-11-09 16:55:11 Age [y:d:h:m:s]: 00:127:18:15:27
Block: 1150091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91143 RingCT/type: yes/0
Extra: 01ad7af26c93dee5ee1453387d81c386cb9062f0139658509e7a1ac4edbb315a05021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83a5a5e94cf9d4c5a9608feb956c016dfe692cf3f2a4998ced4d9a839c54a904 0.600000000000 1635294 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": 1150101, "vin": [ { "gen": { "height": 1150091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83a5a5e94cf9d4c5a9608feb956c016dfe692cf3f2a4998ced4d9a839c54a904" } } ], "extra": [ 1, 173, 122, 242, 108, 147, 222, 229, 238, 20, 83, 56, 125, 129, 195, 134, 203, 144, 98, 240, 19, 150, 88, 80, 158, 122, 26, 196, 237, 187, 49, 90, 5, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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