← previous blocknext block →recent activity

Analyzing

Block #86,192,702

23 transactions · 19 stateful · 2026-07-07 12:30:54 UTC

Parallelism

74/100

Blocked

37%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,192,702  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0ab54c30…b88e

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x4755fafb…859b

0x34b655…2a6f

6 touches
3 conflicts

0xddd7607e…9b4b

0x34b655…2a6f

6 touches
3 conflicts

0x05b1b07a…7a99

0x34b655…2a6f

6 touches
3 conflicts

0x4f715ae2…92a5

0x34b655…2a6f

4 touches
1 conflict

0x5bad3cdf…d4fb

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 0x0ab54c30a6…82b88e

← previous block·next block →recent activity