← previous blocknext block →recent activity
Analyzing
Block #106,216,710
30 transactions · 28 stateful · 2026-09-19 15:47:44 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.53
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,216,710 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w48w59w610w723w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf99856c4…370d
0x34b655…2a6f
16 touches
28 conflicts
0xa8916533…79cd
0x34b655…2a6f
12 touches
15 conflicts
0x38c6ff01…689f
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x310a7246…2dcb
0x34b655…2a6f
10 touches
10 conflicts
0x6f4ff085…45cc
0x34b655…2a6f
8 touches
6 conflicts
0x98ad4ee3…4947
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
28 conflicts on slot 0xf99856c491…9a370d
Audit this contract →
← previous block·next block →recent activity