Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7348189af7901ec5d6d14aea213c1fb7653659a1a973616c84d723afe1ac5e8c

Tx prefix hash: aa1152f1a42b0288a9c099de90bf1f4ff1c83f56ef18037c8d13e19940bbe187
Tx public key: 4a68e8aaef70bae073a657f400124b21fe90984ce17c7f733903d47b744edb29
Timestamp: 1721739233 Timestamp [UCT]: 2024-07-23 12:53:53 Age [y:d:h:m:s]: 00:326:18:20:33
Block: 1071967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233412 RingCT/type: yes/0
Extra: 014a68e8aaef70bae073a657f400124b21fe90984ce17c7f733903d47b744edb2902110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 702c77f6416e8d6197c5980f8cb9bc8aa9123fe931d34b7d5c2d8a7638f0511b 0.600000000000 1544378 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": 1071977, "vin": [ { "gen": { "height": 1071967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "702c77f6416e8d6197c5980f8cb9bc8aa9123fe931d34b7d5c2d8a7638f0511b" } } ], "extra": [ 1, 74, 104, 232, 170, 239, 112, 186, 224, 115, 166, 87, 244, 0, 18, 75, 33, 254, 144, 152, 76, 225, 124, 127, 115, 57, 3, 212, 123, 116, 78, 219, 41, 2, 17, 0, 0, 0, 15, 233, 20, 221, 21, 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