← previous blocknext block →recent activity
Analyzing
Block #106,921,846
25 transactions · 23 stateful · 2026-09-22 02:57:41 UTC
Parallelism
56/100
Blocked
70%
Avg conflicts / tx
2.2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,921,846 · 25 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
1w02w13w24w15w06w17w28w39w210w313w617w318w719w820w921w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccf585fa…e0af
0x34b655…2a6f
14 touches
21 conflicts
0xf1bbd371…e541
0x34b655…2a6f
12 touches
15 conflicts
0x51087f5a…61f7
0x34b655…2a6f
10 touches
10 conflicts
0x8590b692…b267
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x155e52ca…fac7
0x34b655…2a6f
8 touches
6 conflicts
0x579b1425…252a
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
21 conflicts on slot 0xccf585fa3d…5ee0af
Audit this contract →
← previous block·next block →recent activity