← previous blocknext block →recent activity
Analyzing
Block #91,104,544
24 transactions · 19 stateful · 2026-07-28 16:23:53 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,104,544 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w17w28w39w410w511w612w715w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
16 touches
28 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x103be197…826c
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xe82c33ae…a9a5
0xa6afd3…d132
3 touches
1 conflict
0xff9feb1d…4269
0xa6afd3…d132
3 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: 0x48cba278…e2b48b
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity