← previous blocknext block →recent activity
Analyzing
Block #91,796,346
16 transactions · 14 stateful · 2026-07-31 02:26:23 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,796,346 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w29w310w411w112w513w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b30a6e6…b249
0x34b655…2a6f
6 touches
3 conflicts
0xb1b58b33…874f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x3230413b…bc7f
0x34b655…2a6f
4 touches
1 conflict
0x5f5a0edf…ebcc
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0x9fa5be00…fb16
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 0x5b30a6e65f…9bb249
Audit this contract →
← previous block·next block →recent activity