← previous blocknext block →recent activity
Analyzing
Block #106,923,296
41 transactions · 41 stateful · 2026-09-22 03:05:00 UTC
Parallelism
68/100
Blocked
66%
Avg conflicts / tx
2.27
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,923,296 · 41 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w07w28w09w110w011w112w013w114w115w217w423w524w625w726w827w928w1029w1130w1232w333w437w138w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x524f0872…0d12
0x34b655…2a6f
20 touches
45 conflicts
0x206f4379…e08a
0x34b655…2a6f
16 touches
28 conflicts
0x8c572c8c…280b
0x34b655…2a6f
16 touches
28 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0x5070f68d…d86f
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x69411fb3…e36d
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0x524f087203…e70d12
Audit this contract →
← previous block·next block →recent activity