← previous blocknext block →recent activity
Analyzing
Block #106,936,120
32 transactions · 30 stateful · 2026-09-22 04:09:32 UTC
Parallelism
66/100
Blocked
60%
Avg conflicts / tx
1.31
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,936,120 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w08w19w210w011w114w215w318w122w323w424w527w428w729w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x239139d0…ae18
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xb50ef533…79e4
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xfac61869…a560
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 0x239139d009…3dae18
Audit this contract →
← previous block·next block →recent activity