← previous blocknext block →recent activity
Analyzing
Block #106,366,783
27 transactions · 26 stateful · 2026-09-20 04:23:00 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.37
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,366,783 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w09w110w214w015w116w217w218w319w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1927b58…f161
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xed1041a6…f63c
0x34b655…2a6f
14 touches
21 conflicts
0x85ac8cc2…3104
0x34b655…2a6f
8 touches
6 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
8 touches
6 conflicts
0x2c2761c0…476e
0x34b655…2a6f
8 touches
6 conflicts
0x17010c56…97dd
0x6f6493…b480
6 touches
3 conflicts
0x17708471…a168
0x6f6493…b480
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
28 conflicts on slot 0xb1927b5859…36f161
Audit this contract →
← previous block·next block →recent activity