← previous blocknext block →recent activity

Analyzing

Block #86,836,908

21 transactions · 20 stateful · 2026-07-10 12:17:34 UTC

Parallelism

62/100

Blocked

45%

Avg conflicts / tx

1.1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,836,908  ·  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

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0xf1dab3b8…1ab6

0x34b655…2a6f

10 touches
10 conflicts

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0xfdde6236…b2a5

0x34b655…2a6f

10 touches
10 conflicts

0x414d9d7c…e664

0x34b655…2a6f

8 touches
6 conflicts

0x5fee1ba0…2520

0x34b655…2a6f

8 touches
6 conflicts

0x63c900f4…2600

0x34b655…2a6f

8 touches
6 conflicts

0x7523ad90…2ba5

0x34b655…2a6f

8 touches
6 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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity