← previous blocknext block →recent activity
Analyzing
Block #91,096,400
15 transactions · 15 stateful · 2026-07-28 15:42:55 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,096,400 · 15 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
1w02w13w24w05w06w17w28w212w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae28870c…072f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x01078ee0…48e1
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2f8f103b…29f4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d485a88…ca35
0x34b655…2a6f
4 touches
1 conflict
0x63cb32b4…34a4
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
3 conflicts on slot 0xae28870c63…13072f
Audit this contract →
← previous block·next block →recent activity