← previous blocknext block →recent activity

Analyzing

Block #87,518,832

21 transactions · 17 stateful · 2026-07-13 16:17:04 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,518,832  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x4e1ce17e…98a7

0x34b655…2a6f

6 touches
3 conflicts

0xa457c06e…2f06

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x89750670…2dea

0xa6afd3…d132

4 touches
1 conflict

0xb670a63e…ead8

0x34b655…2a6f

4 touches
1 conflict

0xcf827da3…f2a5

0x34b655…2a6f

4 touches
1 conflict

0xfe4e62b8…9ade

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x4e1ce17e14…ed98a7

← previous block·next block →recent activity