← previous blocknext block →recent activity

Analyzing

Block #87,688,247

31 transactions · 28 stateful · 2026-07-14 11:10:19 UTC

Parallelism

81/100

Blocked

32%

Avg conflicts / tx

0.61

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,688,247  ·  31 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x18cf36a6…a3a3

0x34b655…2a6f

6 touches
3 conflicts

0x2fdfe038…c16c

0x34b655…2a6f

6 touches
3 conflicts

0x59dccbd8…2bf6

0x34b655…2a6f

6 touches
3 conflicts

0x61e7b277…fee7

0x34b655…2a6f

6 touches
3 conflicts

0xa86351b8…2c5a

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 0x0733be30d6…38112f

← previous block·next block →recent activity