← previous blocknext block →recent activity

Analyzing

Block #87,513,624

17 transactions · 16 stateful · 2026-07-13 15:42:05 UTC

Parallelism

88/100

Blocked

19%

Avg conflicts / tx

0.24

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #87,513,624  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x05d7fa80…9c9e

0x34b655…2a6f

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xeefeaede…42c7

0x34b655…2a6f

4 touches
1 conflict

0x15f34da3…49ae

0x34b655…2a6f

2 touches
0 conflicts

0x19a49e01…677c

0x34b655…2a6f

2 touches
0 conflicts

0x3b30f216…d17a

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x05d7fa801f…d29c9e

← previous block·next block →recent activity