← previous blocknext block →recent activity
Analyzing
Block #91,161,197
10 transactions · 9 stateful · 2026-07-28 21:08:53 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,161,197 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfce0ddd…ddbd
0x34b655…2a6f
6 touches
3 conflicts
0x5b2d25ba…eb48
0x34b655…2a6f
6 touches
3 conflicts
0x4c623175…29e4
0x34b655…2a6f
6 touches
3 conflicts
0x4688dd30…ef52
0x34b655…2a6f
4 touches
1 conflict
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0x0bd6ae72…5a87
0x34b655…2a6f
4 touches
1 conflict
0x430a9411…e89a
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 0xdfce0dddaa…d8ddbd
Audit this contract →
← previous block·next block →recent activity