← previous blocknext block →recent activity
Analyzing
Block #91,103,851
8 transactions · 6 stateful · 2026-07-28 16:20:24 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,103,851 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb566cc65…214d
0xa6afd3…d132
4 touches
1 conflict
0x07d8b1e8…78c6
0x34b655…2a6f
2 touches
0 conflicts
0x0a9f55a2…ef5d
0x34b655…2a6f
2 touches
0 conflicts
0x0ab6d83d…4965
0x34b655…2a6f
2 touches
0 conflicts
0x154b56c6…3d64
0x34b655…2a6f
2 touches
0 conflicts
0x17636ea2…681e
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 0x38bdc5d3e1…01a632
Audit this contract →
← previous block·next block →recent activity