← previous blocknext block →recent activity

Analyzing

Block #87,730,751

22 transactions · 19 stateful · 2026-07-14 15:55:00 UTC

Parallelism

59/100

Blocked

58%

Avg conflicts / tx

1.55

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,730,751  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xc4de6652…13f4

0x34b655…2a6f

16 touches
28 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0xeeaba9d3…b491

0x34b655…2a6f

8 touches
6 conflicts

0xaa643d44…2122

0x34b655…2a6f

8 touches
6 conflicts

0x67905f6e…02a1

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x747f609d…1555

0x34b655…2a6f

8 touches
6 conflicts

0x97b94d6b…de0d

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 0xc4de665222…6513f4

← previous block·next block →recent activity