← previous blocknext block →recent activity
Analyzing
Block #107,815,292
26 transactions · 22 stateful · 2026-09-25 05:57:11 UTC
Parallelism
69/100
Blocked
41%
Avg conflicts / tx
0.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,815,292 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w19w212w213w314w415w516w617w724w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
10 touches
10 conflicts
0xdd9b4be4…198a
0x34b655…2a6f
8 touches
6 conflicts
0xa23b9051…392f
0x34b655…2a6f
8 touches
6 conflicts
0x2328941c…84d3
0x34b655…2a6f
6 touches
3 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
10 conflicts on slot 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity