← previous blocknext block →recent activity

Analyzing

Block #86,803,498

21 transactions · 17 stateful · 2026-07-10 08:34:03 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,803,498  ·  21 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

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0001

0xfa32f9…f3f0

6 touches
3 conflicts

0x38b5b2ce…c5bb

0xfa32f9…f3f0

6 touches
3 conflicts

0x99f666e3…b2a2

0x3bd359…433a

6 touches
3 conflicts

0x9194f4a3…10b8

0x754704…b603

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

10 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity