← previous blocknext block →recent activity

Analyzing

Block #85,144,071

23 transactions · 20 stateful · 2026-07-02 16:02:05 UTC

Parallelism

74/100

Blocked

40%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,144,071  ·  23 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x7c63ea28…e8af

0x34b655…2a6f

8 touches
6 conflicts

0xed296a95…7d12

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xaa99c369…263d

0x34b655…2a6f

6 touches
3 conflicts

0x3c5e3f6a…1143

0x34b655…2a6f

4 touches
1 conflict

0x5a18edad…54e5

0x34b655…2a6f

4 touches
1 conflict

0x644919d7…9727

0x34b655…2a6f

4 touches
1 conflict

0x64ac7e92…178f

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

6 conflicts on slot 0x7c63ea28d6…76e8af

← previous block·next block →recent activity