← previous blocknext block →recent activity

Analyzing

Block #86,487,145

22 transactions · 20 stateful · 2026-07-08 21:17:58 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.91

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,487,145  ·  22 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

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0x922c7ebd…6600

0xc8689a…ee79

10 touches
10 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

10 touches
10 conflicts

0x9f40a209…1193

0x34b655…2a6f

10 touches
10 conflicts

0xb251976b…4938

0x34b655…2a6f

10 touches
10 conflicts

0xe727ab72…768b

0x34b655…2a6f

6 touches
3 conflicts

0xd25a34fd…3e4d

0x34b655…2a6f

6 touches
3 conflicts

0x761fa0c2…132e

0x34b655…2a6f

6 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

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity