← previous blocknext block →recent activity
Analyzing
Block #106,235,217
41 transactions · 38 stateful · 2026-09-19 17:20:55 UTC
Parallelism
56/100
Blocked
71%
Avg conflicts / tx
4.15
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,235,217 · 41 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
1w02w13w24w35w46w07w18w29w311w414w515w618w721w723w926w1228w1330w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65f8fcff…e6ba
0x34b655…2a6f
22 touches
55 conflicts
0x160f9a70…b139
0x34b655…2a6f
20 touches
45 conflicts
0x94f4eab2…673c
0x34b655…2a6f
20 touches
45 conflicts
0x1a84e266…4f8a
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
14 touches
21 conflicts
0x310a7246…2dcb
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x65f8fcffa0…0ce6ba
Audit this contract →
← previous block·next block →recent activity