← previous blocknext block →recent activity
Analyzing
Block #85,103,968
29 transactions · 19 stateful · 2026-07-02 11:33:55 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,103,968 · 29 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
1w02w13w24w37w08w09w110w211w312w013w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x9d688243…b2dc
0xd32edf…ff58
7 touches
6 conflicts
0x2b093939…9083
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x35ad1637…75b0
0xa6afd3…d132
4 touches
1 conflict
0x36d366fe…7adc
0xa6afd3…d132
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: 0x04fdeac2…f747d7
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity