← previous blocknext block →recent activity

Analyzing

Block #85,146,138

20 transactions · 19 stateful · 2026-07-02 16:15:51 UTC

Parallelism

80/100

Blocked

42%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,146,138  ·  20 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5b353877…605d

0x34b655…2a6f

4 touches
1 conflict

0x9966da31…0d0f

0x34b655…2a6f

4 touches
1 conflict

0x9bd7860c…d01e

0x34b655…2a6f

4 touches
1 conflict

0xcfa965cc…6fcf

0x34b655…2a6f

4 touches
1 conflict

0xd2a592d9…1a96

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

3 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity