← previous blocknext block →recent activity
Analyzing
Block #106,235,701
23 transactions · 22 stateful · 2026-09-19 17:23:21 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,235,701 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w212w313w414w015w117w518w019w120w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80ba129e…037d
0x34b655…2a6f
8 touches
6 conflicts
0xf9470055…bbf8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xaef82336…d052
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xb19129b6…40c4
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: Perpl
6 conflicts on slot 0x80ba129e96…dd037d
Audit this contract →
← previous block·next block →recent activity