← previous blocknext block →recent activity
Analyzing
Block #106,576,808
35 transactions · 33 stateful · 2026-09-20 22:00:04 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,576,808 · 35 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
1w02w13w04w15w26w07w29w110w211w321w122w324w125w326w427w528w429w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38c6ff01…689f
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
10 touches
10 conflicts
0xcd3b2959…afde
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x71a05713…b3ce
0x34b655…2a6f
8 touches
6 conflicts
0x885efce3…7496
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
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
10 conflicts on slot 0x38c6ff017b…61689f
Audit this contract →
← previous block·next block →recent activity