← previous blocknext block →recent activity
Analyzing
Block #106,809,894
33 transactions · 30 stateful · 2026-09-21 17:34:11 UTC
Parallelism
58/100
Blocked
67%
Avg conflicts / tx
2.27
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,809,894 · 33 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w26w07w114w215w216w317w418w319w420w421w522w623w724w826w128w929w1030w1131w1232w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7f01feb3…85be
0x34b655…2a6f
14 touches
21 conflicts
0x24b2ba87…21ff
0x34b655…2a6f
10 touches
10 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
8 touches
6 conflicts
0x88c37cad…1a21
0x34b655…2a6f
8 touches
6 conflicts
0x62885981…5b1f
0x34b655…2a6f
8 touches
6 conflicts
0x08f9abf1…10bf
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity