← previous blocknext block →recent activity
Analyzing
Block #91,070,553
41 transactions · 37 stateful · 2026-07-28 13:32:48 UTC
Parallelism
73/100
Blocked
68%
Avg conflicts / tx
1.8
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,070,553 · 41 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
1w02w13w15w28w39w010w111w212w313w414w219w020w131w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x427d1120…4eb1
0x34b655…2a6f
8 touches
6 conflicts
0x92115abd…ad76
0x34b655…2a6f
8 touches
6 conflicts
0x957c875f…b3f9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity