← previous blocknext block →recent activity

Analyzing

Block #85,987,029

21 transactions · 15 stateful · 2026-07-06 13:37:53 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,987,029  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x077d58c3…8ed7

0x34b655…2a6f

4 touches
1 conflict

0x1bd46462…e65c

0x34b655…2a6f

4 touches
1 conflict

0x1c287db3…e562

0x34b655…2a6f

4 touches
1 conflict

0x5970867d…638a

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7b3f8378…b37d

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity