← previous blocknext block →recent activity
Analyzing
Block #106,235,358
23 transactions · 21 stateful · 2026-09-19 17:21:38 UTC
Parallelism
65/100
Blocked
52%
Avg conflicts / tx
1.74
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,235,358 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w310w412w515w416w517w618w720w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65bb78fd…5476
0x34b655…2a6f
14 touches
21 conflicts
0xac0b4a08…faae
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xf99856c4…370d
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0xb550abea…2729
0x34b655…2a6f
6 touches
3 conflicts
0x30ae635d…5e67
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
21 conflicts on slot 0x65bb78fd33…c55476
Audit this contract →
← previous block·next block →recent activity