← previous blocknext block →recent activity

Analyzing

Block #87,737,187

32 transactions · 21 stateful · 2026-07-14 16:38:03 UTC

Parallelism

72/100

Blocked

43%

Avg conflicts / tx

0.78

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,737,187  ·  32 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

10 touches
10 conflicts

0x94ba9c4a…41d8

0x34b655…2a6f

8 touches
6 conflicts

0x2b7950c1…2342

0x34b655…2a6f

8 touches
6 conflicts

0x3bb680b4…09ef

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x85a88798…f85e

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4a3

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

10 conflicts on slot 0x64aaadbf0a…79f9f3

← previous block·next block →recent activity