← previous blocknext block →recent activity
Analyzing
Block #105,852,834
23 transactions · 23 stateful · 2026-09-18 09:15:20 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,852,834 · 23 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
1w03w06w07w19w110w211w312w413w414w515w616w721w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ae9195f…9cb7
0x34b655…2a6f
10 touches
10 conflicts
0x55192654…91fe
0x34b655…2a6f
10 touches
10 conflicts
0xf9302129…0caa
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd6141cdf…148a
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
10 conflicts on slot 0x1ae9195f63…e69cb7
Audit this contract →
← previous block·next block →recent activity