← previous blocknext block →recent activity
Analyzing
Block #92,062,698
19 transactions · 13 stateful · 2026-08-01 00:46:15 UTC
Parallelism
74/100
Blocked
54%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,062,698 · 19 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
2w04w16w27w18w310w412w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x204378d2…5d9c
0xd32edf…ff58
9 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0xc2658f0e…205c
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
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 0x204378d287…b85d9c
Audit this contract →
← previous block·next block →recent activity