← previous blocknext block →recent activity
Analyzing
Block #105,851,207
25 transactions · 23 stateful · 2026-09-18 09:07:08 UTC
Parallelism
72/100
Blocked
48%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,851,207 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w111w214w015w216w317w418w519w620w021w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdee5a85…e800
0x34b655…2a6f
14 touches
21 conflicts
0x831f75b4…945d
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x932a9590…0b19
0x34b655…2a6f
8 touches
6 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
8 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xc263101a…911c
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0xbdee5a85d6…afe800
Audit this contract →
← previous block·next block →recent activity