← previous blocknext block →recent activity

Analyzing

Block #86,776,571

20 transactions · 18 stateful · 2026-07-10 05:34:17 UTC

Parallelism

75/100

Blocked

39%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,776,571  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x53b1efb4…c65d

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x013c31f5…a718

0x34b655…2a6f

4 touches
1 conflict

0x03cf8a66…08c6

0x34b655…2a6f

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x230a3fb0…e64c

0x34b655…2a6f

4 touches
1 conflict

0x66059cf4…bf4d

0x34b655…2a6f

4 touches
1 conflict

0x6d597594…10d1

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 0x53b1efb4d5…5bc65d

← previous block·next block →recent activity