← previous blocknext block →recent activity
Analyzing
Block #111,931,171
23 transactions · 22 stateful · 2026-10-09 15:24:18 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #111,931,171 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w012w113w216w220w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6c4f8c7…273f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb686e6f5…f6d1
0xc8689a…ee79
4 touches
1 conflict
0xd9d16d34…330f
0x30a88b…7102
2 touches
0 conflicts
0xdc686ec4…237e
0x30a88b…7102
2 touches
0 conflicts
0x2ae58f85…f6e5
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xb6c4f8c7b6…35273f
Audit this contract →
← previous block·next block →recent activity