Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6d80802d0cf87a41596c72c44d9768fb82b8a689f266bab5ff53586cf5478bb

Tx prefix hash: 69064b19035986c3fbeb311198cf586bb2cde8b36f981e38479f42d61c64fb13
Tx public key: d88069a935b76b9cd73b0dec561a4ea9bb7b9525f0071d23004f75857a3a2cd9
Timestamp: 1707548278 Timestamp [UCT]: 2024-02-10 06:57:58 Age [y:d:h:m:s]: 01:045:06:38:11
Block: 954315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293397 RingCT/type: yes/0
Extra: 01d88069a935b76b9cd73b0dec561a4ea9bb7b9525f0071d23004f75857a3a2cd90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98d9b242f1ed25cdbc2a79abd676cabf5296dd18ec109f40a1df1a89c0b3bac7 0.600000000000 1413595 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": 954325, "vin": [ { "gen": { "height": 954315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98d9b242f1ed25cdbc2a79abd676cabf5296dd18ec109f40a1df1a89c0b3bac7" } } ], "extra": [ 1, 216, 128, 105, 169, 53, 183, 107, 156, 215, 59, 13, 236, 86, 26, 78, 169, 187, 123, 149, 37, 240, 7, 29, 35, 0, 79, 117, 133, 122, 58, 44, 217, 2, 17, 0, 0, 0, 2, 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