← previous blocknext block →recent activity

Analyzing

Block #86,792,671

20 transactions · 19 stateful · 2026-07-10 07:21:42 UTC

Parallelism

60/100

Blocked

53%

Avg conflicts / tx

0.9

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,792,671  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1a7

0xb1dbf0…c0d3

8 touches
6 conflicts

0x8a35acfb…d1a8

0xb1dbf0…c0d3

8 touches
6 conflicts

0x1ffe7d94…61ea

0x34b655…2a6f

6 touches
3 conflicts

0x0bc5d643…38d9

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x0bc5d643…38d8

0x34b655…2a6f

6 touches
3 conflicts

0xb6732c22…35cf

0x34b655…2a6f

5 touches
3 conflicts

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 0x0733be30d6…38112f

← previous block·next block →recent activity