← previous blocknext block →recent activity
Analyzing
Block #105,922,293
24 transactions · 24 stateful · 2026-09-18 15:05:48 UTC
Parallelism
67/100
Blocked
63%
Avg conflicts / tx
1.54
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,922,293 · 24 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
1w02w03w14w25w07w39w210w011w112w113w214w316w317w418w519w620w722w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc6615a36…3cf0
0x34b655…2a6f
8 touches
6 conflicts
0x375b6201…9c1e
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x3018a378…d7bb
0x34b655…2a6f
8 touches
6 conflicts
0x97942918…e1a6
0x34b655…2a6f
8 touches
6 conflicts
0xd7d44415…a1d3
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
15 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity