← previous blocknext block →recent activity
Analyzing
Block #96,372,593
18 transactions · 14 stateful · 2026-08-16 02:38:49 UTC
Parallelism
61/100
Blocked
43%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,372,593 · 18 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
1w02w13w24w35w46w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00efc610…2f1c
0xd32edf…ff58
13 touches
21 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0002
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0003
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0009
0x04ddf6…7f33
2 touches
0 conflicts
0x0ef74796…cd18
0x0a3323…0a3c
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
21 conflicts on slot 0x00efc61028…5e2f1c
Audit this contract →
← previous block·next block →recent activity