← previous blocknext block →recent activity
Analyzing
Block #109,064,836
24 transactions · 18 stateful · 2026-09-29 14:52:53 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,064,836 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w18w29w311w416w520w021w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x805ef48d…3d36
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x7a3d5e6f…7864
0x34b655…2a6f
4 touches
1 conflict
0x7d9ef283…ddd1
0x34b655…2a6f
4 touches
1 conflict
0x99a27512…e06b
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
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 0x805ef48df3…ce3d36
Audit this contract →
← previous block·next block →recent activity