← previous blocknext block →recent activity

Analyzing

Block #85,146,108

22 transactions · 20 stateful · 2026-07-02 16:15:39 UTC

Parallelism

77/100

Blocked

35%

Avg conflicts / tx

0.41

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,146,108  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xa2cc62d4…69f6

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x6f59855d…4191

0x34b655…2a6f

4 touches
1 conflict

0x9966da31…0d0f

0x34b655…2a6f

4 touches
1 conflict

0xd2a592d9…1a96

0x34b655…2a6f

4 touches
1 conflict

0xd96c7369…a2c6

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 0xa2cc62d47b…cc69f6

← previous block·next block →recent activity