Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eddf56376d21bfb9bf90b34736cf0176932468e8f4601b8490b19917351881ef

Tx prefix hash: 576215a01c51b06d4fab7f4aabc15210498022f9f60a1f8467f63cdfed8897ff
Tx public key: 6fe3ee27055f96851c5a6e93b36e7ab9ebc6a5ef2e41dd1612b894dbd3f837d6
Timestamp: 1713195866 Timestamp [UCT]: 2024-04-15 15:44:26 Age [y:d:h:m:s]: 00:359:12:01:58
Block: 1001136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257024 RingCT/type: yes/0
Extra: 016fe3ee27055f96851c5a6e93b36e7ab9ebc6a5ef2e41dd1612b894dbd3f837d60211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a781b2853a06ac435637c1d9f7d19ee7443fb91a79d96352afd26270630c09e 0.600000000000 1461638 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": 1001146, "vin": [ { "gen": { "height": 1001136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a781b2853a06ac435637c1d9f7d19ee7443fb91a79d96352afd26270630c09e" } } ], "extra": [ 1, 111, 227, 238, 39, 5, 95, 150, 133, 28, 90, 110, 147, 179, 110, 122, 185, 235, 198, 165, 239, 46, 65, 221, 22, 18, 184, 148, 219, 211, 248, 55, 214, 2, 17, 0, 0, 0, 6, 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