← previous blocknext block →recent activity
Analyzing
Block #109,236,031
21 transactions · 17 stateful · 2026-09-30 05:15:22 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,236,031 · 21 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
2w03w16w27w38w49w510w612w416w517w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x93a8374e…896e
0x34b655…2a6f
6 touches
3 conflicts
0xde58f693…0e66
0x34b655…2a6f
6 touches
3 conflicts
0x7f0cca64…517f
0x34b655…2a6f
4 touches
1 conflict
0x05b498d0…160c
0x34b655…2a6f
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x0d8a97d7…b5d8
0x34b655…2a6f
2 touches
0 conflicts
0x1393df1d…afbd
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity