← previous blocknext block →recent activity
Analyzing
Block #106,931,107
24 transactions · 23 stateful · 2026-09-22 03:44:18 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,931,107 · 24 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
1w02w05w16w28w39w411w212w314w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x2a8ff280…e9ed
0x34b655…2a6f
8 touches
6 conflicts
0x858e40c0…7e30
0x34b655…2a6f
8 touches
6 conflicts
0x69411fb3…e36d
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xc0733aa7…b5df
0x34b655…2a6f
6 touches
3 conflicts
0xc74116ee…6ec0
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity