← previous blocknext block →recent activity
Analyzing
Block #90,885,717
26 transactions · 22 stateful · 2026-07-27 22:02:07 UTC
Parallelism
81/100
Blocked
59%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,885,717 · 26 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
1w02w14w08w19w210w111w212w313w014w115w216w317w418w419w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0x00c39cd6…8c11
0xd32edf…ff58
9 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x731f2745…9370
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb5c4826d…bdd6
0x2b46c0…1669
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
4 touches
1 conflict
0x55012d1a…3907
0x2b46c0…1669
4 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
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity