← previous blocknext block →recent activity
Analyzing
Block #94,912,925
23 transactions · 19 stateful · 2026-08-11 00:01:01 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,912,925 · 23 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
2w03w14w25w36w47w59w010w112w614w015w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad36c9b0…d196
0xd32edf…ff58
13 touches
21 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x0603347b…5872
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
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
21 conflicts on slot 0xad36c9b03f…53d196
Audit this contract →
← previous block·next block →recent activity