← previous blocknext block →recent activity
Analyzing
Block #91,770,622
14 transactions · 14 stateful · 2026-07-31 00:16:59 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,770,622 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w18w29w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36e1467…8393
0x34b655…2a6f
6 touches
3 conflicts
0x641245e3…6323
0xc8689a…ee79
4 touches
1 conflict
0x29a5ecc7…7df7
0x851145…3f07
4 touches
1 conflict
0x3a440312…5522
0x851145…3f07
4 touches
1 conflict
0xb8644937…ed09
0x851145…3f07
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
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 0xc36e14679d…d48393
Audit this contract →
← previous block·next block →recent activity