← previous blocknext block →recent activity
Analyzing
Block #109,131,421
23 transactions · 18 stateful · 2026-09-29 20:28:29 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,131,421 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w38w010w312w413w014w115w121w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x742e5c25…a6b2
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
8 touches
6 conflicts
0x85e2939a…902a
0x34b655…2a6f
6 touches
3 conflicts
0x8c867dbd…24ec
0x34b655…2a6f
6 touches
3 conflicts
0x98dd86bb…1edb
0x34b655…2a6f
6 touches
3 conflicts
0xb51775c0…0c2c
0x34b655…2a6f
6 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
10 conflicts on slot 0x742e5c25e5…73a6b2
Audit this contract →
← previous block·next block →recent activity