← previous blocknext block →recent activity
Analyzing
Block #106,810,596
15 transactions · 15 stateful · 2026-09-21 17:37:43 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,810,596 · 15 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
1w02w13w24w06w37w411w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e6832ca…0340
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9ba5adab…cacc
0x34b655…2a6f
6 touches
3 conflicts
0xc2dbbe3f…ce05
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
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 0x1e6832ca35…920340
Audit this contract →
← previous block·next block →recent activity