← previous blocknext block →recent activity
Analyzing
Block #91,060,911
14 transactions · 14 stateful · 2026-07-28 12:44:18 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,060,911 · 14 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
4w05w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0cd89b3c…836c
0x34b655…2a6f
2 touches
0 conflicts
0x1286d1f7…68df
0x34b655…2a6f
2 touches
0 conflicts
0x2301904e…8503
0x34b655…2a6f
2 touches
0 conflicts
0x28363e9e…1f9f
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 0x69411fb3ba…bce36d
Audit this contract →
← previous block·next block →recent activity