← previous blocknext block →recent activity
Analyzing
Block #106,403,067
28 transactions · 27 stateful · 2026-09-20 07:25:36 UTC
Parallelism
61/100
Blocked
52%
Avg conflicts / tx
1.86
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,403,067 · 28 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w312w413w417w518w619w720w721w822w923w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x611a16a4…f6b1
0x34b655…2a6f
14 touches
21 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
14 touches
21 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
10 touches
10 conflicts
0x6af2981e…5a35
0x34b655…2a6f
10 touches
10 conflicts
0x2d071de0…c86e
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x5d1ac445…5233
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
21 conflicts on slot 0x611a16a4a5…38f6b1
Audit this contract →
← previous block·next block →recent activity