← previous blocknext block →recent activity
Analyzing
Block #94,795,966
37 transactions · 29 stateful · 2026-08-10 14:12:42 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
1.41
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #94,795,966 · 37 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
2w04w112w213w314w415w516w617w718w830w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c1a5c35…4b09
0xd32edf…ff58
17 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x3293a887…43ff
0x1b6862…e19c
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 0x0c1a5c35e5…1c4b09
Audit this contract →
← previous block·next block →recent activity