← previous blocknext block →recent activity
Analyzing
Block #91,386,181
35 transactions · 29 stateful · 2026-07-29 16:01:45 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.11
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,386,181 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w010w111w212w313w015w116w217w318w420w321w427w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x2c75ca93…a569
0x34b655…2a6f
6 touches
3 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
6 touches
3 conflicts
0xf5899760…c130
0x34b655…2a6f
6 touches
3 conflicts
0xb39cb1d8…effa
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity