← previous blocknext block →recent activity
Analyzing
Block #106,217,010
27 transactions · 23 stateful · 2026-09-19 15:49:14 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,217,010 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w29w116w318w419w320w421w522w626w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf99856c4…370d
0x34b655…2a6f
10 touches
10 conflicts
0x6f4ff085…45cc
0x34b655…2a6f
8 touches
6 conflicts
0x5b6af007…0f35
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
6 touches
3 conflicts
0x1d1f4fb6…320b
0x34b655…2a6f
6 touches
3 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xf99856c491…9a370d
Audit this contract →
← previous block·next block →recent activity