← previous blocknext block →recent activity
Analyzing
Block #106,480,667
29 transactions · 28 stateful · 2026-09-20 13:56:12 UTC
Parallelism
38/100
Blocked
71%
Avg conflicts / tx
4.17
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,480,667 · 29 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
1w02w16w210w311w312w414w515w616w717w818w921w1222w1323w1424w1525w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x7cf1f52d…ed62
0x34b655…2a6f
18 touches
36 conflicts
0xc8cb0701…3926
0x34b655…2a6f
16 touches
28 conflicts
0x5e2ea201…12de
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0x1c840894…764a
0x34b655…2a6f
10 touches
10 conflicts
0xda830e9d…9484
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
55 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity