← previous blocknext block →recent activity
Analyzing
Block #106,382,053
33 transactions · 31 stateful · 2026-09-20 05:39:51 UTC
Parallelism
67/100
Blocked
71%
Avg conflicts / tx
1.91
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,382,053 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w07w18w212w013w114w215w317w418w219w320w221w423w524w525w626w727w828w929w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfece6852…70f3
0x34b655…2a6f
18 touches
36 conflicts
0x4984f7be…d515
0x34b655…2a6f
12 touches
15 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
12 touches
15 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
10 touches
10 conflicts
0xfb111bae…5303
0x34b655…2a6f
8 touches
6 conflicts
0xe283e878…7262
0x34b655…2a6f
8 touches
6 conflicts
0xad50d01e…23c8
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
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 0xfece685231…da70f3
Audit this contract →
← previous block·next block →recent activity