← previous blocknext block →recent activity

Analyzing

Block #87,727,536

32 transactions · 23 stateful · 2026-07-14 15:33:31 UTC

Parallelism

72/100

Blocked

43%

Avg conflicts / tx

1.06

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,727,536  ·  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

0x1941b441…5889

0x34b655…2a6f

10 touches
10 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

8 touches
6 conflicts

0x99c5409a…25b7

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xeebaa043…0d3c

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x95c9704c…8a57

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 0x1941b4413e…0c5889

← previous block·next block →recent activity