← previous blocknext block →recent activity
Analyzing
Block #106,466,116
21 transactions · 20 stateful · 2026-09-20 12:42:58 UTC
Parallelism
52/100
Blocked
55%
Avg conflicts / tx
1.95
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,466,116 · 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
2w03w15w07w19w110w211w312w414w516w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1927b58…f161
0x34b655…2a6f
16 touches
28 conflicts
0x7bb6424f…59b8
0x34b655…2a6f
10 touches
10 conflicts
0x29d45f2d…6576
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe44e295a…ecaf
0x34b655…2a6f
8 touches
6 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x21e79ad8…c5db
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 0xb1927b5859…36f161
Audit this contract →
← previous block·next block →recent activity