← previous blocknext block →recent activity
Analyzing
Block #106,389,717
22 transactions · 22 stateful · 2026-09-20 06:18:26 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,389,717 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w210w011w115w216w317w318w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f63f383…6eda
0x34b655…2a6f
8 touches
6 conflicts
0x3208efd0…8e91
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0xb9b077a8…e029
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x5b2cb0c8…c5f6
0x34b655…2a6f
8 touches
6 conflicts
0x000bde1a…e123
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x8f63f383d9…ff6eda
Audit this contract →
← previous block·next block →recent activity