← previous blocknext block →recent activity
Analyzing
Block #91,270,482
23 transactions · 22 stateful · 2026-07-29 06:19:26 UTC
Parallelism
70/100
Blocked
36%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,270,482 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w111w115w216w317w418w519w620w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0xfa76e617…f49b
0x34b655…2a6f
6 touches
3 conflicts
0x609e537a…511d
0x34b655…2a6f
6 touches
3 conflicts
0x4332bc2b…f8c3
0x34b655…2a6f
6 touches
3 conflicts
0xc4ed41b1…6db5
0x34b655…2a6f
6 touches
3 conflicts
0x22f55465…3968
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
10 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity