← previous blocknext block →recent activity
Analyzing
Block #91,403,088
8 transactions · 7 stateful · 2026-07-29 17:26:51 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,403,088 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf18e87f5…6880
0x34b655…2a6f
4 touches
1 conflict
0x2840c278…bbc7
0x34b655…2a6f
4 touches
1 conflict
0x72b8b170…3237
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xaca60768…7272
0x34b655…2a6f
2 touches
0 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
2 touches
0 conflicts
0x58cec012…dcb8
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
1 conflict on slot 0xf18e87f591…356880
Audit this contract →
← previous block·next block →recent activity