← previous blocknext block →recent activity
Analyzing
Block #106,535,364
22 transactions · 21 stateful · 2026-09-20 18:31:30 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,535,364 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w08w09w112w113w214w315w118w020w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x38f283d2…339a
0x34b655…2a6f
6 touches
3 conflicts
0xb2560305…f27d
0x34b655…2a6f
6 touches
3 conflicts
0xe6ac7f90…fc5d
0x34b655…2a6f
6 touches
3 conflicts
0xa705f083…67b4
0x34b655…2a6f
5 touches
3 conflicts
0xb654bd89…a83b
0x34b655…2a6f
5 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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity