← previous blocknext block →recent activity
Analyzing
Block #92,820,863
23 transactions · 22 stateful · 2026-08-03 16:20:39 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,820,863 · 23 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
1w02w13w24w06w07w110w212w213w316w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b9bb58c…e73a
0x34b655…2a6f
10 touches
10 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x779e83bb…edbf
0x34b655…2a6f
6 touches
3 conflicts
0xd53220ed…4737
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x35a09235…9aef
0x34b655…2a6f
4 touches
1 conflict
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 0x3b9bb58cfc…93e73a
Audit this contract →
← previous block·next block →recent activity