← previous blocknext block →recent activity

Analyzing

Block #85,146,032

24 transactions · 18 stateful · 2026-07-02 16:15:08 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,146,032  ·  24 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

0x2549dda6…9e24

0x34b655…2a6f

6 touches
3 conflicts

0xdeddb1c8…0d40

0x34b655…2a6f

6 touches
3 conflicts

0x765cd07a…1018

0x34b655…2a6f

6 touches
3 conflicts

0xf98f45fd…37b1

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x9495bffc…46e6

0x34b655…2a6f

4 touches
1 conflict

0xa678cd56…4fab

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 0x2549dda625…4f9e24

← previous block·next block →recent activity