← previous blocknext block →recent activity

Analyzing

Block #86,456,190

30 transactions · 20 stateful · 2026-07-08 17:50:48 UTC

Parallelism

83/100

Blocked

40%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,456,190  ·  30 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

0x0da39371…1ecd

0x34b655…2a6f

8 touches
6 conflicts

0xed6920b1…1a9f

0xd32edf…ff58

7 touches
6 conflicts

0x5f34fd08…aeb3

0x34b655…2a6f

6 touches
3 conflicts

0x7c6a17fa…e95d

0x34b655…2a6f

6 touches
3 conflicts

0xe1d1f14d…3ffb

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x3af0dd8e…0025

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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 0x0da3937156…891ecd

← previous block·next block →recent activity