← previous blocknext block →recent activity
Analyzing
Block #91,088,096
26 transactions · 20 stateful · 2026-07-28 15:01:07 UTC
Parallelism
85/100
Blocked
60%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,088,096 · 26 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
1w03w04w16w28w39w110w211w315w117w219w020w121w123w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 conflicts
0x989252a1…d812
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x529e53cf…38e4
0xa6afd3…d132
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
6 touches
3 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
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: 0x48cba278…e2b48b
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity