← previous blocknext block →recent activity
Analyzing
Block #91,288,864
18 transactions · 18 stateful · 2026-07-29 07:51:59 UTC
Parallelism
39/100
Blocked
56%
Avg conflicts / tx
2.33
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,288,864 · 18 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
1w02w15w06w27w38w411w512w613w714w815w916w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd2e35622…f491
0x34b655…2a6f
8 touches
6 conflicts
0x87fcd5db…d2e6
0x34b655…2a6f
8 touches
6 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity