Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e2a0032763ad7d9e53c6d8dba538c648bfaed55e2bd4c641600df1731b29dc8

Tx prefix hash: fca6ce5b6fdda8985e0b17a7b057b31dcd963d8b154d1663a5a5c163c602aaec
Tx public key: 9a844e08cd45645cb0fd7944fa70a85f4a4251c2f0ed5bffd86550361c251657
Timestamp: 1749600278 Timestamp [UCT]: 2025-06-11 00:04:38 Age [y:d:h:m:s]: 00:151:10:27:04
Block: 1302391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105914 RingCT/type: yes/0
Extra: 019a844e08cd45645cb0fd7944fa70a85f4a4251c2f0ed5bffd86550361c2516570211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39afd4266415c6ffc28887a7a9d617d024b492cc417c7e68be31f1dabf22be80 0.600000000000 1789962 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": 1302401, "vin": [ { "gen": { "height": 1302391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39afd4266415c6ffc28887a7a9d617d024b492cc417c7e68be31f1dabf22be80" } } ], "extra": [ 1, 154, 132, 78, 8, 205, 69, 100, 92, 176, 253, 121, 68, 250, 112, 168, 95, 74, 66, 81, 194, 240, 237, 91, 255, 216, 101, 80, 54, 28, 37, 22, 87, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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