← previous blocknext block →recent activity
Analyzing
Block #91,151,967
9 transactions · 9 stateful · 2026-07-28 20:22:28 UTC
Parallelism
44/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,151,967 · 9 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
2w03w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0x110bac89…3e1f
0x34b655…2a6f
2 touches
0 conflicts
0x38a2a7bd…4a70
0x34b655…2a6f
2 touches
0 conflicts
0x4c7cd861…3c63
0x34b655…2a6f
2 touches
0 conflicts
0x528329a7…dfe7
0x34b655…2a6f
2 touches
0 conflicts
0x6b899aa5…a7a6
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
3 conflicts on slot 0xb983466539…cee363
Audit this contract →
← previous block·next block →recent activity