← previous blocknext block →recent activity

Analyzing

Block #87,577,731

21 transactions · 19 stateful · 2026-07-13 22:51:33 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,577,731  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x16dd4651…e88f

0x34b655…2a6f

4 touches
1 conflict

0x1a5d321d…a474

0x34b655…2a6f

4 touches
1 conflict

0x2f702750…347d

0x34b655…2a6f

4 touches
1 conflict

0x30faf03c…78b1

0x34b655…2a6f

4 touches
1 conflict

0x38befc08…20c8

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity