← previous blocknext block →recent activity
Analyzing
Block #106,577,081
24 transactions · 21 stateful · 2026-09-20 22:01:26 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,577,081 · 24 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
2w07w08w19w012w115w216w217w318w419w520w621w723w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a5dc0db…f558
0x34b655…2a6f
16 touches
28 conflicts
0x110a3804…f842
0x34b655…2a6f
12 touches
15 conflicts
0x588380ee…0a5c
0x34b655…2a6f
10 touches
10 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 conflicts
0x3cf50d44…961b
0x34b655…2a6f
6 touches
3 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x58e5797b…33f8
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
28 conflicts on slot 0x2a5dc0dbab…30f558
Audit this contract →
← previous block·next block →recent activity