Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f66c65ed41a2e78f848756d88e46e03d004654b9d710c6f4e6a4347dd20783e

Tx prefix hash: 9794ae0be8c687550ef71098696110982e60c93b892284eb75d3e2252ee4868c
Tx public key: d6c337e5d5edcc2ac8ef46519d7a5c047fb92d842a0fba236f934e0787cdbdb5
Timestamp: 1716915863 Timestamp [UCT]: 2024-05-28 17:04:23 Age [y:d:h:m:s]: 00:294:17:46:27
Block: 1032001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210654 RingCT/type: yes/0
Extra: 01d6c337e5d5edcc2ac8ef46519d7a5c047fb92d842a0fba236f934e0787cdbdb50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6f3cc843a0f7229e88de0a23eda17e6db84e9132e68ee1559ff02790e760ade 0.600000000000 1500450 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": 1032011, "vin": [ { "gen": { "height": 1032001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6f3cc843a0f7229e88de0a23eda17e6db84e9132e68ee1559ff02790e760ade" } } ], "extra": [ 1, 214, 195, 55, 229, 213, 237, 204, 42, 200, 239, 70, 81, 157, 122, 92, 4, 127, 185, 45, 132, 42, 15, 186, 35, 111, 147, 78, 7, 135, 205, 189, 181, 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