← previous blocknext block →recent activity
Analyzing
Block #106,456,766
23 transactions · 21 stateful · 2026-09-20 11:55:56 UTC
Parallelism
61/100
Blocked
43%
Avg conflicts / tx
1.83
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,456,766 · 23 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
3w07w08w111w112w213w314w415w516w617w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xba33378a…f1df
0x34b655…2a6f
10 touches
10 conflicts
0xfb111bae…5303
0x34b655…2a6f
10 touches
10 conflicts
0x2a21beda…27eb
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
8 touches
6 conflicts
0x30ae635d…5e67
0x34b655…2a6f
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity