← previous blocknext block →recent activity
Analyzing
Block #91,128,851
15 transactions · 13 stateful · 2026-07-28 18:26:10 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,128,851 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w38w410w212w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58ae9c0f…d6c8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa779293b…5e59
0x34b655…2a6f
8 touches
6 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x20a8fb67…1310
0x34b655…2a6f
6 touches
3 conflicts
0x5cac4871…32e6
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x58ae9c0f47…7cd6c8
Audit this contract →
← previous block·next block →recent activity