← previous blocknext block →recent activity
Analyzing
Block #98,571,213
31 transactions · 26 stateful · 2026-08-23 20:26:48 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,571,213 · 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
1w03w010w011w012w113w214w319w122w023w125w126w227w429w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51b3eb2e…f604
0xd32edf…ff58
9 touches
10 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
6 touches
3 conflicts
0x12197aa6…37a5
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x2379c5ed…e740
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
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
10 conflicts on slot 0x51b3eb2e16…7af604
Audit this contract →
← previous block·next block →recent activity