← previous blocknext block →recent activity
Analyzing
Block #85,179,514
21 transactions · 19 stateful · 2026-07-02 19:58:01 UTC
Parallelism
71/100
Blocked
32%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,179,514 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w08w113w014w115w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x987aeb55…0e2a
0xa6afd3…d132
4 touches
1 conflict
0x11431f9d…42c5
0x34b655…2a6f
4 touches
1 conflict
0x1e635221…f46c
0x34b655…2a6f
4 touches
1 conflict
0x2b111712…0e59
0x34b655…2a6f
4 touches
1 conflict
0x5ad3280d…16bb
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity