← previous blocknext block →recent activity
Analyzing
Block #91,063,801
13 transactions · 13 stateful · 2026-07-28 12:58:50 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,063,801 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x9b5f80e5…d4a6
0x34b655…2a6f
6 touches
3 conflicts
0xe00608f8…edc2
0x34b655…2a6f
4 touches
1 conflict
0xffb2bfcf…b92a
0x34b655…2a6f
4 touches
1 conflict
0x266a2581…acae
0x34b655…2a6f
4 touches
1 conflict
0x266a2581…acaf
0x34b655…2a6f
4 touches
1 conflict
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0x6f4e7625…aba5
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity