← previous blocknext block →recent activity
Analyzing
Block #109,131,255
11 transactions · 11 stateful · 2026-09-29 20:27:39 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #109,131,255 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0dc3f489…6afe
0x065c9d…c394
2 touches
0 conflicts
0x3f4ee312…c8e6
0x065c9d…c394
2 touches
0 conflicts
0x79e2a84f…d355
0x065c9d…c394
2 touches
0 conflicts
0xe50f7dbc…f5d2
0x065c9d…c394
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
1 conflict on slot 0xb9868b5233…c6c77f
Audit this contract →
← previous block·next block →recent activity