← previous blocknext block →recent activity
Analyzing
Block #110,198,136
20 transactions · 20 stateful · 2026-10-03 13:58:22 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #110,198,136 · 20 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
1w02w13w24w35w417w018w119w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
12 touches
15 conflicts
0x3be6459e…270b
0x34b655…2a6f
10 touches
10 conflicts
0x8b7e5c4e…5fae
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xe2d50773…c39e
0x34b655…2a6f
10 touches
10 conflicts
0xdad13823…6798
0x37db7f…ec7b
10 touches
10 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
10 touches
10 conflicts
0x241b55d6…e0fa
0x34b655…2a6f
10 touches
10 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 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity