← previous blocknext block →recent activity
Analyzing
Block #106,373,118
35 transactions · 32 stateful · 2026-09-20 04:54:53 UTC
Parallelism
48/100
Blocked
72%
Avg conflicts / tx
3.2
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,373,118 · 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
2w03w15w06w18w29w310w411w514w315w416w519w620w722w924w1125w1227w1429w1630w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9a6e112…69cc
0x34b655…2a6f
26 touches
78 conflicts
0xac0b4a08…faae
0x34b655…2a6f
14 touches
21 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
14 touches
21 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
12 touches
15 conflicts
0x524f0872…0d12
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x8d664414…3344
0x34b655…2a6f
8 touches
6 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
78 conflicts on slot 0xc9a6e112ce…9769cc
Audit this contract →
← previous block·next block →recent activity