← previous blocknext block →recent activity

Analyzing

Block #86,083,519

21 transactions · 18 stateful · 2026-07-07 00:22:02 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,083,519  ·  21 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

0x1aaf4996…65ec

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00ae3e89…8322

0xd32edf…ff58

7 touches
6 conflicts

0x8d4c0bb9…ccd3

0x34b655…2a6f

4 touches
1 conflict

0xbf077403…b465

0x34b655…2a6f

4 touches
1 conflict

0xd8834cf3…0004

0x34b655…2a6f

4 touches
1 conflict

0x03ce88d7…ea0d

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

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 0x1aaf499609…4665ec

← previous block·next block →recent activity