← previous blocknext block →recent activity
Analyzing
Block #91,125,425
14 transactions · 13 stateful · 2026-07-28 18:08:56 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.21
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,125,425 · 14 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
2w03w04w16w27w110w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc0e9c8…3ae6
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x3d4a4a17…e015
0x34b655…2a6f
6 touches
3 conflicts
0xb9c84c75…b267
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x5cc0e9c8b0…1d3ae6
Audit this contract →
← previous block·next block →recent activity