← previous blocknext block →recent activity

Analyzing

Block #86,830,359

24 transactions · 20 stateful · 2026-07-10 11:33:46 UTC

Parallelism

79/100

Blocked

40%

Avg conflicts / tx

0.46

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,830,359  ·  24 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

0xa6b89ebb…a66e

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4c22021d…f8a7

0x34b655…2a6f

4 touches
1 conflict

0x4e3abeff…18eb

0x34b655…2a6f

4 touches
1 conflict

0x6047836f…681e

0x34b655…2a6f

4 touches
1 conflict

0x7239a7a0…e541

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 0xa6b89ebbaf…5fa66e

← previous block·next block →recent activity