← previous blocknext block →recent activity

Analyzing

Block #86,822,599

26 transactions · 24 stateful · 2026-07-10 10:41:54 UTC

Parallelism

58/100

Blocked

71%

Avg conflicts / tx

2.12

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #86,822,599  ·  26 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

16 touches
28 conflicts

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x0f4cddfd…3085

0x34b655…2a6f

8 touches
6 conflicts

0x8a67173b…d00f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5523e84b…0ce4

0x34b655…2a6f

6 touches
3 conflicts

0x231ccc13…a7c6

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

← previous block·next block →recent activity