← previous blocknext block →recent activity

Analyzing

Block #86,621,851

22 transactions · 20 stateful · 2026-07-09 12:19:42 UTC

Parallelism

73/100

Blocked

35%

Avg conflicts / tx

0.59

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,621,851  ·  22 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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x22bc4ea4…5c8a

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x41d3bfa5…523e

0x34b655…2a6f

4 touches
1 conflict

0x511ecf07…8ed0

0x34b655…2a6f

4 touches
1 conflict

0x5e2ea201…12de

0x34b655…2a6f

4 touches
1 conflict

0x63c900f4…2600

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