← previous blocknext block →recent activity
Analyzing
Block #91,422,977
23 transactions · 19 stateful · 2026-07-29 19:07:14 UTC
Parallelism
78/100
Blocked
37%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,422,977 · 23 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
5w06w110w112w213w315w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x16f065f1…d172
0x34b655…2a6f
4 touches
1 conflict
0x2c390858…b1ed
0x34b655…2a6f
4 touches
1 conflict
0x418f6232…2de6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5312cced…82bf
0x34b655…2a6f
4 touches
1 conflict
0x536bd330…4625
0x34b655…2a6f
4 touches
1 conflict
0x589623ea…8ce2
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity