← previous blocknext block →recent activity
Analyzing
Block #91,088,093
48 transactions · 36 stateful · 2026-07-28 15:01:06 UTC
Parallelism
81/100
Blocked
64%
Avg conflicts / tx
1.6
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #91,088,093 · 48 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w29w311w412w513w632w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
16 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x989252a1…d812
0xa6afd3…d132
10 touches
10 conflicts
0x5778d110…d2e6
0xc8689a…ee79
10 touches
10 conflicts
0x529e53cf…38e4
0xa6afd3…d132
10 touches
10 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 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
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity