← previous blocknext block →recent activity
Analyzing
Block #91,189,876
16 transactions · 16 stateful · 2026-07-28 23:33:10 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,189,876 · 16 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
1w02w13w04w15w29w211w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc0e9c8…3ae6
0x34b655…2a6f
10 touches
10 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
0x6fbc2e5a…e69c
0x34b655…2a6f
6 touches
3 conflicts
0x9a573905…60cf
0x34b655…2a6f
6 touches
3 conflicts
0x7ea8c5c0…cf57
0x34b655…2a6f
4 touches
1 conflict
0x94f2c3b4…4ef6
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
10 conflicts on slot 0x5cc0e9c8b0…1d3ae6
Audit this contract →
← previous block·next block →recent activity