← previous blocknext block →recent activity
Analyzing
Block #109,132,404
25 transactions · 23 stateful · 2026-09-29 20:33:25 UTC
Parallelism
68/100
Blocked
35%
Avg conflicts / tx
1.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,132,404 · 25 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
2w011w017w118w219w320w421w522w623w724w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
12 touches
15 conflicts
0xf5dc501b…831c
0x34b655…2a6f
12 touches
15 conflicts
0xd739490d…821e
0x34b655…2a6f
10 touches
10 conflicts
0x1e334ac0…11d3
0x34b655…2a6f
9 touches
10 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
8 touches
6 conflicts
0x181fbbee…c1ba
0x34b655…2a6f
5 touches
3 conflicts
0xa05768d5…824e
0x34b655…2a6f
5 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity