← previous blocknext block →recent activity

Analyzing

Block #87,753,782

20 transactions · 18 stateful · 2026-07-14 18:29:04 UTC

Parallelism

60/100

Blocked

50%

Avg conflicts / tx

1.35

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,753,782  ·  20 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

0x9001f549…089d

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xb1d403a3…e612

0x34b655…2a6f

8 touches
6 conflicts

0x2f461725…5ab2

0x34b655…2a6f

6 touches
3 conflicts

0x3e8b3a49…53ee

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x5597fdd8…3f39

0x34b655…2a6f

6 touches
3 conflicts

0x58620f29…db5a

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

15 conflicts on slot 0x9001f5497d…54089d

← previous block·next block →recent activity