← previous blocknext block →recent activity
Analyzing
Block #109,132,244
21 transactions · 19 stateful · 2026-09-29 20:32:37 UTC
Parallelism
52/100
Blocked
63%
Avg conflicts / tx
2.81
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #109,132,244 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w612w713w714w819w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x742e5c25…a6b2
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0019
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0029
0x1b6862…e19c
18 touches
36 conflicts
0x6235638c…6437
0x1b6862…e19c
18 touches
36 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0x1465bab6…6297
0xd32edf…ff58
17 touches
36 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
36 conflicts on slot 0x742e5c25e5…73a6b2
Audit this contract →
← previous block·next block →recent activity