← previous blocknext block →recent activity
Analyzing
Block #85,528,644
19 transactions · 16 stateful · 2026-07-04 10:43:05 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,528,644 · 19 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
1w02w13w28w09w110w211w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea4316bc…6b4f
0x34b655…2a6f
6 touches
3 conflicts
0x3b1362ff…9c03
0xd32edf…ff58
5 touches
3 conflicts
0xcd81cc7b…8da0
0x34b655…2a6f
4 touches
1 conflict
0xc01211ba…799c
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3181bd2d…cf15
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: Perpl
3 conflicts on slot 0xea4316bcc7…a66b4f
Audit this contract →
← previous block·next block →recent activity