← previous blocknext block →recent activity

Analyzing

Block #86,246,085

24 transactions · 19 stateful · 2026-07-07 18:27:27 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,246,085  ·  24 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

0xf7d37192…0710

0xd32edf…ff58

5 touches
3 conflicts

0x85eb1316…bb9e

0x34b655…2a6f

4 touches
1 conflict

0xa6b89ebb…a66e

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd93edb3f…94ec

0x34b655…2a6f

4 touches
1 conflict

0xe2a664b0…304f

0x34b655…2a6f

4 touches
1 conflict

0xa6e50da3…13e1

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