← previous blocknext block →recent activity
Analyzing
Block #86,240,184
22 transactions · 19 stateful · 2026-07-07 17:47:59 UTC
Parallelism
59/100
Blocked
58%
Avg conflicts / tx
1.77
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,240,184 · 22 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w613w717w818w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x680ff34c…5764
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xed863ec8…90dd
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
36 conflicts on slot 0x680ff34c08…505764
Audit this contract →
← previous block·next block →recent activity