Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5943bda5135a39081d990a7ae8cba4a10a08a8b728581fe54db727174c808eb3

Tx prefix hash: 51cd61550edd391e8978c1173e7a3ec6dedd70c2c4cf7ce2ab1c4bf53a008a97
Tx public key: c4cffe98eeb3adf946ae6e419147cfe4c9a054f1778d286eeb76942a3ce90da0
Timestamp: 1719883449 Timestamp [UCT]: 2024-07-02 01:24:09 Age [y:d:h:m:s]: 01:172:13:09:05
Block: 1056579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381915 RingCT/type: yes/0
Extra: 01c4cffe98eeb3adf946ae6e419147cfe4c9a054f1778d286eeb76942a3ce90da0021100000002ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a7d46a712061d600c9bceb349f91461c42d574837a72b3d4846c55c03d3d90c 0.600000000000 1526994 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": 1056589, "vin": [ { "gen": { "height": 1056579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a7d46a712061d600c9bceb349f91461c42d574837a72b3d4846c55c03d3d90c" } } ], "extra": [ 1, 196, 207, 254, 152, 238, 179, 173, 249, 70, 174, 110, 65, 145, 71, 207, 228, 201, 160, 84, 241, 119, 141, 40, 110, 235, 118, 148, 42, 60, 233, 13, 160, 2, 17, 0, 0, 0, 2, 221, 211, 219, 145, 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