← previous blocknext block →recent activity
Analyzing
Block #109,177,285
20 transactions · 14 stateful · 2026-09-30 00:19:40 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,177,285 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w512w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x951a2c8c…86af
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x6235638c…6438
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity