Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7fcc7b5f97194e233dfa45bc7344d70102f0769da2402987bcaf58bf4814fe0

Tx prefix hash: f8aa7410d497e7cdb517a5b79db9fb42e78d78225ca9f88c3c8a6ca53a6d09dc
Tx public key: 9f58015df6d21435d258273e8696ef4c2e8d82286e3b05c1eb88e04bc76816f1
Timestamp: 1679862446 Timestamp [UCT]: 2023-03-26 20:27:26 Age [y:d:h:m:s]: 02:023:18:25:51
Block: 725697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538518 RingCT/type: yes/0
Extra: 019f58015df6d21435d258273e8696ef4c2e8d82286e3b05c1eb88e04bc76816f1021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.214387493000 dcy

stealth address amount amount idx
00: f74675fa6f20c2a347e6f62f3366418aaeec6e181ad5e79f57051cb48b0e2900 3.214387493000 1170868 of 0

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": 725707, "vin": [ { "gen": { "height": 725697 } } ], "vout": [ { "amount": 3214387493, "target": { "key": "f74675fa6f20c2a347e6f62f3366418aaeec6e181ad5e79f57051cb48b0e2900" } } ], "extra": [ 1, 159, 88, 1, 93, 246, 210, 20, 53, 210, 88, 39, 62, 134, 150, 239, 76, 46, 141, 130, 40, 110, 59, 5, 193, 235, 136, 224, 75, 199, 104, 22, 241, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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