Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f102c050fb625b189db8949357f877dbd6d94aa0bc006a0db16a199ea243c0eb

Tx prefix hash: eb4f5b137b538ab07f6749b94bd207fe7aad05e3787c217378185e365d33a509
Tx public key: c344ca088bbf4aa26215ba8e1f038120c3702db32e26cdd77b9a593275dac060
Timestamp: 1705443225 Timestamp [UCT]: 2024-01-16 22:13:45 Age [y:d:h:m:s]: 01:108:16:32:34
Block: 936855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338792 RingCT/type: yes/0
Extra: 01c344ca088bbf4aa26215ba8e1f038120c3702db32e26cdd77b9a593275dac0600211000000257a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ac3972868d803ae1c9ff851b21f8ceb60c3c1b969bfde2bb89a9f4b52a52c17 0.600000000000 1394897 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": 936865, "vin": [ { "gen": { "height": 936855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ac3972868d803ae1c9ff851b21f8ceb60c3c1b969bfde2bb89a9f4b52a52c17" } } ], "extra": [ 1, 195, 68, 202, 8, 139, 191, 74, 162, 98, 21, 186, 142, 31, 3, 129, 32, 195, 112, 45, 179, 46, 38, 205, 215, 123, 154, 89, 50, 117, 218, 192, 96, 2, 17, 0, 0, 0, 37, 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