← previous blocknext block →recent activity

Analyzing

Block #87,517,963

25 transactions · 22 stateful · 2026-07-13 16:11:11 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,517,963  ·  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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x0f068b13…fb19

0x34b655…2a6f

4 touches
1 conflict

0x25329a48…4e00

0x34b655…2a6f

4 touches
1 conflict

0x34731dbd…e467

0x34b655…2a6f

4 touches
1 conflict

0x4b43f348…e4a6

0x34b655…2a6f

4 touches
1 conflict

0x61757a59…d89f

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

3 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity