← previous blocknext block →recent activity
Analyzing
Block #91,384,166
13 transactions · 13 stateful · 2026-07-29 15:51:37 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,384,166 · 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
2w04w16w27w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d6df589…3a0b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x1ea2b1f6…1d57
0x34b655…2a6f
6 touches
3 conflicts
0xdc7b9eda…e616
0x34b655…2a6f
4 touches
1 conflict
0x1ea2b1f6…1d58
0x34b655…2a6f
4 touches
1 conflict
0x2e095751…39dc
0x34b655…2a6f
4 touches
1 conflict
0x33649c4f…b327
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 0x1d6df58933…573a0b
Audit this contract →
← previous block·next block →recent activity