← previous blocknext block →recent activity
Analyzing
Block #84,140,183
21 transactions · 14 stateful · 2026-06-28 00:27:56 UTC
Parallelism
76/100
Blocked
36%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,140,183 · 21 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
1w02w13w24w35w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e7d405a…77d3
0xd32edf…ff58
9 touches
10 conflicts
0xf8480e2a…dff3
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
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: FastLane: FastLaneAuctionHandler
10 conflicts on slot 0x0e7d405a69…be77d3
Audit this contract →
← previous block·next block →recent activity