← previous blocknext block →recent activity
Analyzing
Block #91,256,546
20 transactions · 19 stateful · 2026-07-29 05:08:38 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,256,546 · 20 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
1w03w04w16w17w212w313w415w016w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
10 touches
10 conflicts
0xd2469bfd…d034
0x34b655…2a6f
6 touches
3 conflicts
0x5efd7300…d8a5
0x34b655…2a6f
6 touches
3 conflicts
0x159cff26…7665
0x34b655…2a6f
6 touches
3 conflicts
0xb801c606…d524
0x34b655…2a6f
6 touches
3 conflicts
0x7e06d07b…36af
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity