← previous blocknext block →recent activity
Analyzing
Block #91,138,444
20 transactions · 19 stateful · 2026-07-28 19:14:25 UTC
Parallelism
45/100
Blocked
58%
Avg conflicts / tx
1.65
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,138,444 · 20 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w48w59w212w013w614w715w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x4bc1abab…5874
0x34b655…2a6f
6 touches
3 conflicts
0xf1b9adf0…fa78
0x34b655…2a6f
5 touches
3 conflicts
0x647014d3…c91f
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
21 conflicts on slot 0xb4e0a934b9…435fc7
Audit this contract →
← previous block·next block →recent activity