Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e9e9c05b7c2d28439a7c385384d8a39516f3a709c4a0ebc105903c53499aaae

Tx prefix hash: 2d41349025d94972d0ef0d13d6d39e5ca8f4132d4f88c936449c0e66765ef664
Tx public key: f236b0dff423a61f1d165148873be63bb22f18e495f320d3466a525b8921e95c
Timestamp: 1753436714 Timestamp [UCT]: 2025-07-25 09:45:14 Age [y:d:h:m:s]: 00:106:01:37:10
Block: 1332999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74609 RingCT/type: yes/0
Extra: 01f236b0dff423a61f1d165148873be63bb22f18e495f320d3466a525b8921e95c021100000005ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f46cdeeded0f73f4ef509f690f51dabe852a4c9e9d7000a9f8751ae141a3bcdd 0.600000000000 1820798 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": 1333009, "vin": [ { "gen": { "height": 1332999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f46cdeeded0f73f4ef509f690f51dabe852a4c9e9d7000a9f8751ae141a3bcdd" } } ], "extra": [ 1, 242, 54, 176, 223, 244, 35, 166, 31, 29, 22, 81, 72, 135, 59, 230, 59, 178, 47, 24, 228, 149, 243, 32, 211, 70, 106, 82, 91, 137, 33, 233, 92, 2, 17, 0, 0, 0, 5, 239, 34, 20, 133, 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