← previous blocknext block →recent activity

Analyzing

Block #87,662,654

23 transactions · 19 stateful · 2026-07-14 08:19:17 UTC

Parallelism

78/100

Blocked

37%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,662,654  ·  23 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

0xc8fec9ca…2d60

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x0804b2ba…8a77

0x34b655…2a6f

6 touches
3 conflicts

0x2f0c7a17…9360

0x34b655…2a6f

4 touches
1 conflict

0x2f0c7a17…9361

0x34b655…2a6f

4 touches
1 conflict

0x3b56f79b…310f

0x34b655…2a6f

4 touches
1 conflict

0x457cca76…23b0

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

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 0xc8fec9cacc…f42d60

← previous block·next block →recent activity