← previous blocknext block →recent activity
Analyzing
Block #91,416,801
13 transactions · 12 stateful · 2026-07-29 18:36:10 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,416,801 · 13 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
4w06w18w29w310w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdd225b0…7a70
0x34b655…2a6f
8 touches
6 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0xfcc19724…4e34
0x34b655…2a6f
4 touches
1 conflict
0x0ea46b1d…c9a4
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x7e7de6d7…48be
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
2 touches
0 conflicts
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 0xcdd225b0fa…9d7a70
Audit this contract →
← previous block·next block →recent activity