← previous blocknext block →recent activity

Analyzing

Block #87,066,094

24 transactions · 23 stateful · 2026-07-11 13:49:10 UTC

Parallelism

38/100

Blocked

70%

Avg conflicts / tx

3.54

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #87,066,094  ·  24 txs across 15 waves  ·  depth 15
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

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

22 touches
55 conflicts

0xb9bc1dfc…6bfb

0x34b655…2a6f

16 touches
28 conflicts

0x41e2ea73…ddf8

0x34b655…2a6f

14 touches
21 conflicts

0xfaef08b1…0696

0x34b655…2a6f

14 touches
21 conflicts

0x727fbce7…0c80

0x34b655…2a6f

12 touches
15 conflicts

0x922c7ebd…6600

0xc8689a…ee79

12 touches
15 conflicts

0x326a02b5…8dad

0x34b655…2a6f

12 touches
15 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

12 touches
15 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

55 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity