← previous blocknext block →recent activity

Analyzing

Block #87,596,270

24 transactions · 20 stateful · 2026-07-14 00:55:34 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

1.04

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,596,270  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x206fb8db…a146

0x34b655…2a6f

12 touches
15 conflicts

0x17c70f19…23a7

0x34b655…2a6f

8 touches
6 conflicts

0x20a110e8…918d

0x34b655…2a6f

8 touches
6 conflicts

0x21158693…63e2

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x308ebcfd…135b

0x34b655…2a6f

8 touches
6 conflicts

0x46fdb575…fe2d

0x34b655…2a6f

8 touches
6 conflicts

0x5cb53fc0…c7f4

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

15 conflicts on slot 0x206fb8db95…b8a146

← previous block·next block →recent activity