← previous blocknext block →recent activity
Analyzing
Block #109,137,349
18 transactions · 18 stateful · 2026-09-29 20:58:18 UTC
Parallelism
56/100
Blocked
67%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,137,349 · 18 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
1w02w15w26w37w38w49w510w511w612w313w114w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd77db191…497c
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c0
0x1b6862…e19c
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x5d80cd54…a58c
0xd32edf…ff58
7 touches
6 conflicts
0x5c421c70…c2ec
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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
10 conflicts on slot 0xd77db191ba…5d497c
Audit this contract →
← previous block·next block →recent activity