← previous blocknext block →recent activity
Analyzing
Block #99,197,001
20 transactions · 18 stateful · 2026-08-26 01:24:30 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,197,001 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w211w012w013w114w015w117w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x45f562b2…9294
0x2b46c0…1669
4 touches
1 conflict
0x8488f10f…9353
0x2b46c0…1669
4 touches
1 conflict
0x8488f10f…9354
0x2b46c0…1669
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
4 touches
1 conflict
0xc20bd100…8b0e
0x2b46c0…1669
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity