← previous blocknext block →recent activity

Analyzing

Block #87,759,238

28 transactions · 22 stateful · 2026-07-14 19:05:32 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.5

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #87,759,238  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xffc2f21e…b393

0x34b655…2a6f

8 touches
6 conflicts

0xf2112d98…bb04

0x34b655…2a6f

6 touches
5 conflicts

0x28c62bca…b746

0x34b655…2a6f

6 touches
3 conflicts

0x2f461725…5ab2

0x34b655…2a6f

6 touches
3 conflicts

0x3fde350e…8d43

0x34b655…2a6f

6 touches
3 conflicts

0x747f609d…1555

0x34b655…2a6f

6 touches
3 conflicts

0x9001f549…089d

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity