← previous blocknext block →recent activity

Analyzing

Block #86,850,010

21 transactions · 17 stateful · 2026-07-10 13:45:05 UTC

Parallelism

62/100

Blocked

59%

Avg conflicts / tx

1.81

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,850,010  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x7e5ea60a…c4aa

0x34b655…2a6f

16 touches
28 conflicts

0xec7fe04a…3c56

0x34b655…2a6f

10 touches
10 conflicts

0x9e70dadd…810d

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x346e6e22…8deb

0x34b655…2a6f

6 touches
3 conflicts

0x9e70dadd…810e

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

28 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity