← previous blocknext block →recent activity
Analyzing
Block #105,844,206
21 transactions · 19 stateful · 2026-09-18 08:31:53 UTC
Parallelism
62/100
Blocked
37%
Avg conflicts / tx
1.62
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,844,206 · 21 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
1w011w012w113w214w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
14 touches
21 conflicts
0xf778799e…2698
0x34b655…2a6f
14 touches
21 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0x5fad6fee…7714
0x34b655…2a6f
8 touches
6 conflicts
0xf5425ed0…ee68
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xef475eb4…7f84
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