← previous blocknext block →recent activity

Analyzing

Block #87,518,947

23 transactions · 19 stateful · 2026-07-13 16:17:50 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.87

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,518,947  ·  23 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

0x4cabb80a…46bf

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x89750670…2dea

0xa6afd3…d132

8 touches
6 conflicts

0xb4c35fcd…43ae

0xa6afd3…d132

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xdb067026…9eb8

0x2b46c0…1669

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

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 0x4cabb80a0e…7546bf

← previous block·next block →recent activity