← previous blocknext block →recent activity
Analyzing
Block #106,373,135
19 transactions · 17 stateful · 2026-09-20 04:54:58 UTC
Parallelism
68/100
Blocked
65%
Avg conflicts / tx
1.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,373,135 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w09w111w212w313w415w516w417w518w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9a6e112…69cc
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x364036f4…10de
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xb0e4f69d…34e3
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
10 conflicts on slot 0xc9a6e112ce…9769cc
Audit this contract →
← previous block·next block →recent activity