← previous blocknext block →recent activity
Analyzing
Block #91,039,220
21 transactions · 19 stateful · 2026-07-28 10:55:10 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
1.57
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,039,220 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w38w49w513w616w717w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
14 touches
21 conflicts
0x4efae872…6aa8
0x34b655…2a6f
10 touches
10 conflicts
0xcd51eb25…31f9
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x9cf9008a…d826
0x34b655…2a6f
8 touches
6 conflicts
0xc7954a60…d294
0x34b655…2a6f
8 touches
6 conflicts
0xe8843e0b…90af
0x34b655…2a6f
8 touches
6 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity