Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a72a6a285b34a39cb745af5bd1040f282a1053940a4569f16b210c3e523d997b

Tx prefix hash: 79754ef66c83bb76de7e8c163c84571ee9ad04084c35b2c55ec05192c4afbd13
Tx public key: e56a23233fb912ac6fd630a786e18c0384660a3e46f4ba21c1ec2adf5e0ab65a
Timestamp: 1709052876 Timestamp [UCT]: 2024-02-27 16:54:36 Age [y:d:h:m:s]: 01:281:16:33:35
Block: 966804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460096 RingCT/type: yes/0
Extra: 01e56a23233fb912ac6fd630a786e18c0384660a3e46f4ba21c1ec2adf5e0ab65a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f7385d708b23b6c2355a513989de053c433a9539e5c972e93f5660546187446 0.600000000000 1426575 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": 966814, "vin": [ { "gen": { "height": 966804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f7385d708b23b6c2355a513989de053c433a9539e5c972e93f5660546187446" } } ], "extra": [ 1, 229, 106, 35, 35, 63, 185, 18, 172, 111, 214, 48, 167, 134, 225, 140, 3, 132, 102, 10, 62, 70, 244, 186, 33, 193, 236, 42, 223, 94, 10, 182, 90, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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