Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93cc560ddd4f26613c52c7d3a3cb866ad22d2b3aefcf41e198742ed1c12ac92e

Tx prefix hash: bf0fb424f957df93b17b657d1eb72b81259e42f66b0ab1606ca0a902c337a40c
Tx public key: ac718960790b4832da06b7c05f9f870fd3d96ff1f01e4e1d0d4d4e384ccba13a
Timestamp: 1723108619 Timestamp [UCT]: 2024-08-08 09:16:59 Age [y:d:h:m:s]: 00:140:02:32:26
Block: 1083330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100245 RingCT/type: yes/0
Extra: 01ac718960790b4832da06b7c05f9f870fd3d96ff1f01e4e1d0d4d4e384ccba13a021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 443666ca1d067cbc37a1c0ab82273bef68f49c7216a76f0e0e1be5ba340e1b65 0.600000000000 1557201 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": 1083340, "vin": [ { "gen": { "height": 1083330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "443666ca1d067cbc37a1c0ab82273bef68f49c7216a76f0e0e1be5ba340e1b65" } } ], "extra": [ 1, 172, 113, 137, 96, 121, 11, 72, 50, 218, 6, 183, 192, 95, 159, 135, 15, 211, 217, 111, 241, 240, 30, 78, 29, 13, 77, 78, 56, 76, 203, 161, 58, 2, 17, 0, 0, 0, 9, 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