← previous blocknext block →recent activity
Analyzing
Block #106,917,381
35 transactions · 34 stateful · 2026-09-22 02:35:13 UTC
Parallelism
48/100
Blocked
65%
Avg conflicts / tx
3.06
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,917,381 · 35 txs across 18 waves · depth 18
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
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w29w310w411w512w613w714w815w916w1017w1122w1627w1728w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea79e6d3…68ad
0x34b655…2a6f
24 touches
66 conflicts
0x42522e76…2592
0x34b655…2a6f
20 touches
45 conflicts
0x4db105b4…056c
0x34b655…2a6f
19 touches
45 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
18 touches
36 conflicts
0x81d2de5b…f95e
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0xea2d3331…6e36
0x1b6862…e19c
6 touches
3 conflicts
0xaa48aaa0…73fe
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
66 conflicts on slot 0xea79e6d350…ec68ad
Audit this contract →
← previous block·next block →recent activity