← previous blocknext block →recent activity
Analyzing
Block #106,568,870
19 transactions · 18 stateful · 2026-09-20 21:20:07 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,568,870 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w110w011w212w314w415w516w618w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a3edcbd…1b23
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x4089d428…b018
0x34b655…2a6f
10 touches
10 conflicts
0x5ed07c7e…69aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xd996735f…8734
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x8590b692…b267
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
15 conflicts on slot 0x7a3edcbdc9…191b23
Audit this contract →
← previous block·next block →recent activity