← previous blocknext block →recent activity

Analyzing

Block #87,711,678

25 transactions · 18 stateful · 2026-07-14 13:47:15 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,711,678  ·  25 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

0x7fa1794c…3323

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x5170a218…3a84

0xc8689a…ee79

6 touches
3 conflicts

0x0ba865dd…a249

0x34b655…2a6f

6 touches
3 conflicts

0x882b1bd8…10b5

0x34b655…2a6f

6 touches
3 conflicts

0x9f366352…d55b

0x34b655…2a6f

6 touches
3 conflicts

0xc0b9bd73…7f1c

0x34b655…2a6f

6 touches
3 conflicts

0xd9072021…db76

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 0x7fa1794cc8…6c3323

← previous block·next block →recent activity