← previous blocknext block →recent activity
Analyzing
Block #91,395,926
14 transactions · 13 stateful · 2026-07-29 16:50:46 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,395,926 · 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
2w04w06w17w19w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a573905…60cf
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5a1cf363…de38
0x34b655…2a6f
4 touches
1 conflict
0xa457c06e…2f06
0x34b655…2a6f
4 touches
1 conflict
0xb577a4a7…a670
0x34b655…2a6f
4 touches
1 conflict
0xb852cf41…12b6
0x34b655…2a6f
4 touches
1 conflict
0xbfc7fb1b…7dfb
0x34b655…2a6f
4 touches
1 conflict
0x1ebd4745…6509
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 0x9a5739053f…5260cf
Audit this contract →
← previous block·next block →recent activity