← previous blocknext block →recent activity
Analyzing
Block #105,841,068
20 transactions · 19 stateful · 2026-09-18 08:15:58 UTC
Parallelism
55/100
Blocked
53%
Avg conflicts / tx
1.7
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,841,068 · 20 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
2w05w06w17w18w29w310w411w512w613w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xb482658a…e4f5
0x34b655…2a6f
12 touches
15 conflicts
0x9c623cfd…b42b
0x34b655…2a6f
12 touches
15 conflicts
0x90a021f0…f922
0x34b655…2a6f
10 touches
10 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
10 touches
10 conflicts
0x422cccbc…9b18
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x00216970…a965
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity