← previous blocknext block →recent activity

Analyzing

Block #87,256,937

24 transactions · 23 stateful · 2026-07-12 11:05:31 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,256,937  ·  24 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

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd99d25df…ecd8

0x34b655…2a6f

6 touches
3 conflicts

0xe214f7d0…5600

0x34b655…2a6f

6 touches
3 conflicts

0x2dff59d9…f5e6

0x34b655…2a6f

6 touches
3 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

6 touches
3 conflicts

0x1a843f41…02aa

0x34b655…2a6f

6 touches
3 conflicts

0x7ba216b2…eec1

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

6 conflicts on slot 0x92385428ad…dc6941

← previous block·next block →recent activity