← previous blocknext block →recent activity
Analyzing
Block #91,541,357
10 transactions · 9 stateful · 2026-07-30 05:03:43 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,541,357 · 10 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
0x663ff9d7…a77f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x3230413b…bc7f
0x34b655…2a6f
2 touches
0 conflicts
0x58940b94…acb3
0x34b655…2a6f
2 touches
0 conflicts
0x6a1959f8…47e7
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0x75d6a8e9…67a7
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 0x663ff9d796…aaa77f
Audit this contract →
← previous block·next block →recent activity