← previous blocknext block →recent activity
Analyzing
Block #93,389,870
31 transactions · 23 stateful · 2026-08-05 16:03:55 UTC
Parallelism
77/100
Blocked
57%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,389,870 · 31 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w310w413w014w115w216w517w618w324w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f4c10b1…9363
0xd32edf…ff58
13 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x033cf007…136d
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x7d4f80a4…bb19
0x1b6862…e19c
6 touches
3 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
21 conflicts on slot 0x4f4c10b1be…669363
Audit this contract →
← previous block·next block →recent activity