← previous blocknext block →recent activity
Analyzing
Block #91,088,737
18 transactions · 17 stateful · 2026-07-28 15:04:21 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,088,737 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w19w110w011w212w315w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7036f81…789a
0x34b655…2a6f
8 touches
6 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
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
6 conflicts on slot 0xf7036f814d…ee789a
Audit this contract →
← previous block·next block →recent activity