← previous blocknext block →recent activity
Analyzing
Block #91,097,741
23 transactions · 21 stateful · 2026-07-28 15:49:40 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,097,741 · 23 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
3w05w06w17w212w119w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xae28870c…072f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x103be197…826c
0xa6afd3…d132
4 touches
1 conflict
0x66a11a3b…0ee9
0xa6afd3…d132
4 touches
1 conflict
0x931f6224…004f
0x065c9d…c394
2 touches
0 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity