← previous blocknext block →recent activity
Analyzing
Block #91,568,226
11 transactions · 11 stateful · 2026-07-30 07:18:52 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,568,226 · 11 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
2w03w15w26w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f5a0edf…ebcc
0x34b655…2a6f
4 touches
1 conflict
0x8924af83…d0ed
0x34b655…2a6f
4 touches
1 conflict
0xb1966336…fead
0x34b655…2a6f
4 touches
1 conflict
0xbcbb6bba…1c92
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd30f9e74…d404
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
1 conflict on slot 0x5f5a0edfcc…1eebcc
Audit this contract →
← previous block·next block →recent activity