← previous blocknext block →recent activity
Analyzing
Block #91,001,662
13 transactions · 11 stateful · 2026-07-28 07:45:52 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,001,662 · 13 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
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bfc83e5…e8eb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x159aac52…c583
0x34b655…2a6f
2 touches
0 conflicts
0x1bb56de3…732e
0x34b655…2a6f
2 touches
0 conflicts
0x41359ed6…5a7f
0x34b655…2a6f
2 touches
0 conflicts
0x60dc7b78…d1d5
0x34b655…2a6f
2 touches
0 conflicts
0x6b3c1134…cbf4
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 0x0bfc83e5be…cde8eb
Audit this contract →
← previous block·next block →recent activity