← previous blocknext block →recent activity
Analyzing
Block #91,011,836
9 transactions · 9 stateful · 2026-07-28 08:37:21 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,011,836 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
2 touches
0 conflicts
0x4881fece…1fc5
0x34b655…2a6f
2 touches
0 conflicts
0x5babb0df…9cf9
0x34b655…2a6f
2 touches
0 conflicts
0x60dc7b78…d1d5
0x34b655…2a6f
2 touches
0 conflicts
0x62d6e82b…a750
0x34b655…2a6f
2 touches
0 conflicts
0x6d94d7d6…6ed4
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x442e26a30f…bbe968
Audit this contract →
← previous block·next block →recent activity