← previous blocknext block →recent activity

Analyzing

Block #86,330,919

21 transactions · 18 stateful · 2026-07-08 03:53:54 UTC

Parallelism

71/100

Blocked

39%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,330,919  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

4 touches
1 conflict

0x0d2de0f6…e6c6

0x34b655…2a6f

4 touches
1 conflict

0x213a54fa…c85f

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x3e505a15…70f8

0x34b655…2a6f

4 touches
1 conflict

0x4bfdcd51…9b58

0x34b655…2a6f

4 touches
1 conflict

0x4c04ce68…d007

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity