← previous blocknext block →recent activity
Analyzing
Block #109,131,364
22 transactions · 17 stateful · 2026-09-29 20:28:11 UTC
Parallelism
73/100
Blocked
41%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,131,364 · 22 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
2w07w18w210w217w018w119w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x742e5c25…a6b2
0x34b655…2a6f
10 touches
10 conflicts
0x224a332f…c89e
0x34b655…2a6f
6 touches
3 conflicts
0x8c867dbd…24ec
0x34b655…2a6f
6 touches
3 conflicts
0x932f2399…b7fe
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb51775c0…0c2c
0x34b655…2a6f
4 touches
1 conflict
0xb7e8b0c4…dec3
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity