← previous blocknext block →recent activity
Analyzing
Block #106,386,196
26 transactions · 25 stateful · 2026-09-20 06:00:43 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
1.73
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,386,196 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w17w18w210w311w412w513w614w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c549b52…80c6
0x34b655…2a6f
16 touches
28 conflicts
0xa98e9641…560c
0x34b655…2a6f
16 touches
28 conflicts
0x2130a548…c1de
0x34b655…2a6f
10 touches
10 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
10 touches
10 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
8 touches
6 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
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
28 conflicts on slot 0x1c549b52ab…3980c6
Audit this contract →
← previous block·next block →recent activity