← previous blocknext block →recent activity
Analyzing
Block #91,100,372
15 transactions · 13 stateful · 2026-07-28 16:02:54 UTC
Parallelism
60/100
Blocked
46%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,100,372 · 15 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
2w03w04w15w26w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f46ea6…18c4
0x34b655…2a6f
6 touches
3 conflicts
0x99701186…1cbf
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc014bcf3…3ac7
0x34b655…2a6f
6 touches
3 conflicts
0x6719a767…9d62
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7b3f8378…b37d
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
3 conflicts on slot 0x63f46ea6ba…5318c4
Audit this contract →
← previous block·next block →recent activity