Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8be0b1c2faf1b000f9b6b084e45f37ba54133a0f7b87605fa75fcc96b53f891

Tx prefix hash: 499c72bc05355290fcf85e3ed4b0023b0b4cbf3a08ae2eb4385917e08d8c0b1d
Tx public key: 1090e55092bebe121aed682095d66f84c70501118300c85f9b5086fbea9b8994
Timestamp: 1723339406 Timestamp [UCT]: 2024-08-11 01:23:26 Age [y:d:h:m:s]: 00:260:10:18:40
Block: 1085237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186039 RingCT/type: yes/0
Extra: 011090e55092bebe121aed682095d66f84c70501118300c85f9b5086fbea9b8994021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6c927c0d385e63d18c6ef48d329b26d4cb9180c37a0e6ee6d7c801245f0861a 0.600000000000 1559780 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": 1085247, "vin": [ { "gen": { "height": 1085237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6c927c0d385e63d18c6ef48d329b26d4cb9180c37a0e6ee6d7c801245f0861a" } } ], "extra": [ 1, 16, 144, 229, 80, 146, 190, 190, 18, 26, 237, 104, 32, 149, 214, 111, 132, 199, 5, 1, 17, 131, 0, 200, 95, 155, 80, 134, 251, 234, 155, 137, 148, 2, 17, 0, 0, 0, 3, 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