← previous blocknext block →recent activity

Analyzing

Block #86,779,354

24 transactions · 20 stateful · 2026-07-10 05:52:50 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,779,354  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x01a08f7d…dec6

0x34b655…2a6f

4 touches
1 conflict

0x0d846676…b323

0x34b655…2a6f

4 touches
1 conflict

0x19ba76c3…6342

0x34b655…2a6f

4 touches
1 conflict

0x39c051d9…0418

0x34b655…2a6f

4 touches
1 conflict

0x427f51fd…bd80

0x34b655…2a6f

4 touches
1 conflict

0x466b2761…714f

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0xfaef08b108…f90696

← previous block·next block →recent activity