← previous blocknext block →recent activity
Analyzing
Block #91,017,374
17 transactions · 16 stateful · 2026-07-28 09:05:14 UTC
Parallelism
59/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,017,374 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w38w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa69b7638…7f86
0x34b655…2a6f
6 touches
3 conflicts
0xf96c955b…06e8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x95dd1dda…bc0e
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 0xa69b763841…4f7f86
Audit this contract →
← previous block·next block →recent activity