← previous blocknext block →recent activity

Analyzing

Block #87,589,180

31 transactions · 26 stateful · 2026-07-14 00:08:07 UTC

Parallelism

58/100

Blocked

62%

Avg conflicts / tx

1.58

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #87,589,180  ·  31 txs across 13 waves  ·  depth 13
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

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

0x6fe7d366…78ff

0x34b655…2a6f

16 touches
28 conflicts

0xd93edb3f…94ec

0x34b655…2a6f

12 touches
15 conflicts

0x21c9fd73…dae4

0x34b655…2a6f

10 touches
10 conflicts

0x34d95d94…3a16

0x34b655…2a6f

10 touches
10 conflicts

0x5b145de0…367c

0xc8689a…ee79

10 touches
10 conflicts

0x201679bc…0414

0x34b655…2a6f

10 touches
10 conflicts

0x875164c2…f8a2

0x34b655…2a6f

10 touches
10 conflicts

0x9fd37234…2731

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

28 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity