← previous blocknext block →recent activity

Analyzing

Block #87,331,754

18 transactions · 17 stateful · 2026-07-12 19:25:45 UTC

Parallelism

56/100

Blocked

53%

Avg conflicts / tx

1.39

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,331,754  ·  18 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

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0x0e9a70ab…e67c

0x34b655…2a6f

10 touches
10 conflicts

0x922c7ebd…6600

0xc8689a…ee79

10 touches
10 conflicts

0x3d4584df…ffed

0x34b655…2a6f

10 touches
10 conflicts

0x548145a9…cfce

0x34b655…2a6f

10 touches
10 conflicts

0x567bb003…113a

0x34b655…2a6f

10 touches
10 conflicts

0x63b15849…80b2

0x34b655…2a6f

10 touches
10 conflicts

0x63c900f4…2600

0x34b655…2a6f

10 touches
10 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

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity