← previous blocknext block →recent activity

Analyzing

Block #86,233,846

23 transactions · 20 stateful · 2026-07-07 17:05:41 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,233,846  ·  23 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

8 touches
6 conflicts

0xdfa159d0…1576

0x065c9d…c394

6 touches
3 conflicts

0xcda18b0b…6a4c

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xffb8950c…23c6

0x34b655…2a6f

4 touches
1 conflict

0x70cc97af…14f1

0x34b655…2a6f

4 touches
1 conflict

0xac0b4a08…faae

0x34b655…2a6f

4 touches
1 conflict

0xc3cda232…10dd

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity