← previous blocknext block →recent activity
Analyzing
Block #79,123,268
30 transactions · 19 stateful · 2026-06-04 18:27:36 UTC
Parallelism
87/100
Blocked
53%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #79,123,268 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w012w013w015w216w118w219w321w323w024w125w026w127w228w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2051568…f2b4
0xd32edf…ff58
7 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0003
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0005
0x5afd3e…7620
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
6 conflicts on slot 0xd20515682b…92f2b4
Audit this contract →
← previous block·next block →recent activity