← previous blocknext block →recent activity
Analyzing
Block #94,903,883
15 transactions · 14 stateful · 2026-08-10 23:15:33 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,903,883 · 15 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
1w02w13w24w36w17w28w310w411w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e7a2786…d03a
0xd32edf…ff58
9 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x731189c2…d0b0
0x851145…3f07
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0x758f26d7…858f
0x01bff4…1071
4 touches
1 conflict
0x6c26d635…1bbf
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 0x2e7a278691…53d03a
Audit this contract →
← previous block·next block →recent activity