← previous blocknext block →recent activity
Analyzing
Block #106,199,510
27 transactions · 26 stateful · 2026-09-19 14:21:07 UTC
Parallelism
74/100
Blocked
58%
Avg conflicts / tx
1.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,199,510 · 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
1w02w14w05w16w27w38w49w510w612w114w218w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0a4e112…f855
0x34b655…2a6f
14 touches
21 conflicts
0xe098738f…9bbe
0x34b655…2a6f
10 touches
10 conflicts
0xda7447d5…97be
0x34b655…2a6f
10 touches
10 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0x79254875…30ac
0x34b655…2a6f
8 touches
6 conflicts
0x9d449fac…d895
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xcfe180d7…b5a4
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
21 conflicts on slot 0xb0a4e112ff…8cf855
Audit this contract →
← previous block·next block →recent activity