← previous blocknext block →recent activity

Analyzing

Block #85,987,492

24 transactions · 19 stateful · 2026-07-06 13:40:58 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,987,492  ·  24 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

0x7a2fc410…c088

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xffb8950c…23c6

0x34b655…2a6f

6 touches
3 conflicts

0x0ad4dbe8…ae93

0x34b655…2a6f

6 touches
3 conflicts

0x157dbfb2…4089

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

6 touches
3 conflicts

0xfa1a8731…ca65

0x34b655…2a6f

6 touches
3 conflicts

0x90d81b88…3a34

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

6 conflicts on slot 0x7a2fc4107b…25c088

← previous block·next block →recent activity