← previous blocknext block →recent activity
Analyzing
Block #85,143,835
26 transactions · 17 stateful · 2026-07-02 16:00:30 UTC
Parallelism
85/100
Blocked
47%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,143,835 · 26 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
2w05w16w211w014w015w116w217w322w324w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x3e1c3586…83d7
0xa6afd3…d132
8 touches
6 conflicts
0x987aeb55…0e2a
0xa6afd3…d132
8 touches
6 conflicts
0x3fde350e…8d43
0x34b655…2a6f
6 touches
3 conflicts
0x6167486f…db40
0x34b655…2a6f
6 touches
3 conflicts
0x79fade94…7f93
0x34b655…2a6f
6 touches
3 conflicts
0xa678cd56…4fab
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity