← previous blocknext block →recent activity
Analyzing
Block #90,883,824
16 transactions · 15 stateful · 2026-07-27 21:52:35 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,883,824 · 16 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
2w05w16w27w38w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf908f13…89dd
0xd32edf…ff58
9 touches
10 conflicts
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x1ffbe7b6…b886
0x34b655…2a6f
4 touches
1 conflict
0x8a1e429b…f85c
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xfe37eae6…7bd0
0x34b655…2a6f
3 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
2 touches
0 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: FastLane: FastLaneAuctionHandler
10 conflicts on slot 0xaf908f1338…bf89dd
Audit this contract →
← previous block·next block →recent activity