← previous blocknext block →recent activity

Analyzing

Block #87,311,435

19 transactions · 19 stateful · 2026-07-12 17:09:51 UTC

Parallelism

47/100

Blocked

63%

Avg conflicts / tx

1.89

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #87,311,435  ·  19 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x64aaadbf…f9f3

0x34b655…2a6f

12 touches
15 conflicts

0x3ef0952c…762d

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ad

0xb1dbf0…c0d3

6 touches
3 conflicts

0x37ee30c9…9e70

0x34b655…2a6f

6 touches
3 conflicts

0x9001f549…089d

0x34b655…2a6f

6 touches
3 conflicts

0xa112f315…1a92

0x34b655…2a6f

6 touches
3 conflicts

0xe85e763f…3b25

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 0x64aaadbf0a…79f9f3

← previous block·next block →recent activity