← previous blocknext block →recent activity
Analyzing
Block #91,779,777
25 transactions · 22 stateful · 2026-07-31 01:03:03 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,779,777 · 25 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
1w04w07w08w110w211w315w116w419w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0629cebb…4e45
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x31b06932…8a2e
0x34b655…2a6f
4 touches
1 conflict
0x3c7908ed…47c8
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 0x0629cebb8e…b84e45
Audit this contract →
← previous block·next block →recent activity