← previous blocknext block →recent activity
Analyzing
Block #85,414,539
12 transactions · 12 stateful · 2026-07-03 22:03:32 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,414,539 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb5de3c7…c64d
0xa6afd3…d132
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x541f8b20…bbf5
0x065c9d…c394
4 touches
1 conflict
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x026ad723…ab79
0x0594c7…a3be
2 touches
0 conflicts
0xb34eccdf…1e77
0x0594c7…a3be
2 touches
0 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
1 conflict on slot 0xbb5de3c7a2…40c64d
Audit this contract →
← previous block·next block →recent activity