← previous blocknext block →recent activity
Analyzing
Block #106,420,874
21 transactions · 21 stateful · 2026-09-20 08:55:13 UTC
Parallelism
52/100
Blocked
43%
Avg conflicts / tx
2.14
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,420,874 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w210w313w414w515w616w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60be5cbc…7218
0x34b655…2a6f
18 touches
36 conflicts
0x2c2761c0…476e
0x34b655…2a6f
12 touches
15 conflicts
0xc5184473…3d1a
0x34b655…2a6f
12 touches
15 conflicts
0x524f0872…0d12
0x34b655…2a6f
10 touches
10 conflicts
0x4118bd12…924a
0x34b655…2a6f
10 touches
10 conflicts
0x1ab9db16…85dc
0x34b655…2a6f
8 touches
6 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0xb1314528…f332
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
36 conflicts on slot 0x60be5cbc32…9f7218
Audit this contract →
← previous block·next block →recent activity