← previous blocknext block →recent activity
Analyzing
Block #91,295,606
9 transactions · 9 stateful · 2026-07-29 08:25:54 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,295,606 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfadc00f2…fb6e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
4 touches
1 conflict
0x731d7308…fd26
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 0xfadc00f275…32fb6e
Audit this contract →
← previous block·next block →recent activity