Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b85aea64890ebb12d825e104a50c0548cf327ea5cd489a7a64ce8151814dc0ba

Tx prefix hash: 035933be556c8abe6cb429b5f181ebe1d2f69ddfa08b0f65e989895ea57348a8
Tx public key: c8b252454177fb79d1efcc3e5ae3ba5db8b379b1170214bcc93bcc71a88831b0
Timestamp: 1705189726 Timestamp [UCT]: 2024-01-13 23:48:46 Age [y:d:h:m:s]: 01:095:18:06:31
Block: 934756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329548 RingCT/type: yes/0
Extra: 01c8b252454177fb79d1efcc3e5ae3ba5db8b379b1170214bcc93bcc71a88831b00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09ad4693a94151db3cb90e2355d0d82a6c2d3ff634391c0213f3a8e1e9e6532f 0.600000000000 1392772 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": 934766, "vin": [ { "gen": { "height": 934756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09ad4693a94151db3cb90e2355d0d82a6c2d3ff634391c0213f3a8e1e9e6532f" } } ], "extra": [ 1, 200, 178, 82, 69, 65, 119, 251, 121, 209, 239, 204, 62, 90, 227, 186, 93, 184, 179, 121, 177, 23, 2, 20, 188, 201, 59, 204, 113, 168, 136, 49, 176, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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