← previous blocknext block →recent activity

Analyzing

Block #86,249,956

29 transactions · 21 stateful · 2026-07-07 18:53:22 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.34

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,249,956  ·  29 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

0xab23ac87…fb2b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xa6b89ebb…a66e

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x76d1e78d…7877

0x40c49f…2af0

4 touches
1 conflict

0xb1bdf54a…e244

0x40c49f…2af0

4 touches
1 conflict

0xd6aabe89…92f5

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 0xab23ac87f2…9afb2b

← previous block·next block →recent activity