← previous blocknext block →recent activity
Analyzing
Block #110,308,162
11 transactions · 11 stateful · 2026-10-03 23:12:02 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,308,162 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4656137…5858
0x34b655…2a6f
8 touches
6 conflicts
0x8c211514…b757
0x34b655…2a6f
8 touches
6 conflicts
0x2fde3e82…2035
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x4ab23153…8f44
0x34b655…2a6f
4 touches
1 conflict
0xcbbc3148…18b0
0x80ef19…40df
4 touches
1 conflict
0xdb99c0d8…99df
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
6 conflicts on slot 0xb465613784…635858
Audit this contract →
← previous block·next block →recent activity