← previous blocknext block →recent activity
Analyzing
Block #109,177,616
9 transactions · 8 stateful · 2026-09-30 00:21:20 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,177,616 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a7026db…025f
0x34b655…2a6f
6 touches
3 conflicts
0x5565353a…6c9e
0x34b655…2a6f
6 touches
3 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xf6cc3bca…ef71
0x34b655…2a6f
6 touches
3 conflicts
0xd9293f55…8b69
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0053
0x1b6862…e19c
4 touches
1 conflict
0x063eca74…c2e2
0x1b6862…e19c
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
3 conflicts on slot 0x2a7026db22…44025f
Audit this contract →
← previous block·next block →recent activity