← previous blocknext block →recent activity
Analyzing
Block #106,235,064
32 transactions · 30 stateful · 2026-09-19 17:20:09 UTC
Parallelism
72/100
Blocked
60%
Avg conflicts / tx
1.84
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,235,064 · 32 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w26w37w48w517w622w723w824w225w826w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70e89205…5121
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0xf99856c4…370d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa81592a3…f569
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x70e89205f2…125121
Audit this contract →
← previous block·next block →recent activity