← previous blocknext block →recent activity
Analyzing
Block #85,049,812
26 transactions · 20 stateful · 2026-07-02 05:32:01 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,049,812 · 26 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
1w02w13w27w010w011w112w215w016w317w118w123w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x158accef…4c74
0xa6afd3…d132
8 touches
6 conflicts
0xe41f8863…29a4
0xa6afd3…d132
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
6 touches
3 conflicts
0x40970e69…da50
0x69df8a…6292
6 touches
3 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
6 touches
3 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
6 touches
3 conflicts
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: Kuru Exchange: Market-WETH/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity