← previous blocknext block →recent activity
Analyzing
Block #83,653,436
31 transactions · 26 stateful · 2026-06-25 18:22:53 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,653,436 · 31 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
3w04w15w27w08w110w013w314w115w017w121w225w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1678f19…f42f
0xd32edf…ff58
9 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x1b0da1d0…0f41
0x065c9d…c394
3 touches
1 conflict
0xdd7c68fd…b34f
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0003
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 0xa1678f191a…5ef42f
Audit this contract →
← previous block·next block →recent activity