← previous blocknext block →recent activity
Analyzing
Block #91,434,751
23 transactions · 22 stateful · 2026-07-29 20:07:21 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,434,751 · 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
1w02w14w05w16w07w110w211w012w315w116w220w421w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8eae8a3…bacc
0x34b655…2a6f
8 touches
6 conflicts
0xacd1b162…bee6
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x1641b47c…19ac
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x4b8db3ce…d59b
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
6 conflicts on slot 0xe8eae8a323…64bacc
Audit this contract →
← previous block·next block →recent activity