← previous blocknext block →recent activity
Analyzing
Block #90,788,088
34 transactions · 24 stateful · 2026-07-27 13:50:51 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,788,088 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w28w39w410w122w023w126w129w130w231w032w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55012d1a…3907
0x2b46c0…1669
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 conflicts
0x538f77c2…a9e7
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
8 touches
6 conflicts
0xad3ef711…4f2b
0x2b46c0…1669
6 touches
3 conflicts
0xa987699f…eabe
0x2b46c0…1669
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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: 0x2b46c08c…ec1669
6 conflicts on slot 0x55012d1a33…d93907
Audit this contract →
← previous block·next block →recent activity