← previous blocknext block →recent activity
Analyzing
Block #81,102,213
24 transactions · 19 stateful · 2026-06-13 22:37:37 UTC
Parallelism
83/100
Blocked
26%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,102,213 · 24 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
4w05w112w015w118w219w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x444a810b…1618
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x936f37a8…9812
0xa6afd3…d132
4 touches
1 conflict
0xe5a10916…8ad0
0xa6afd3…d132
4 touches
1 conflict
0xfd72a574…e07a
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
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 0x444a810b74…3c1618
Audit this contract →
← previous block·next block →recent activity