← previous blocknext block →recent activity

Analyzing

Block #86,691,334

21 transactions · 16 stateful · 2026-07-09 20:04:56 UTC

Parallelism

71/100

Blocked

56%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,691,334  ·  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

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x3ba014e3…35d5

0x34b655…2a6f

6 touches
3 conflicts

0x23253ea8…e0a4

0x34b655…2a6f

4 touches
1 conflict

0x274ac476…27fa

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x64792a0c…d2b7

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

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 0x92385428ad…dc6941

← previous block·next block →recent activity