← previous blocknext block →recent activity
Analyzing
Block #107,442,293
25 transactions · 24 stateful · 2026-09-23 22:37:43 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,442,293 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w28w19w310w411w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
6 touches
3 conflicts
0xb066c72c…87d2
0x34b655…2a6f
6 touches
3 conflicts
0x1081c9a0…4368
0x34b655…2a6f
4 touches
1 conflict
0x190b178a…c154
0x34b655…2a6f
4 touches
1 conflict
0xac75fbf6…f09d
0x34b655…2a6f
4 touches
1 conflict
0x097cee83…0878
0x34b655…2a6f
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: USDC (USDC)
6 conflicts on slot 0xd17580f913…78ece1
Audit this contract →
← previous block·next block →recent activity