← previous blocknext block →recent activity

Analyzing

Block #87,912,672

17 transactions · 17 stateful · 2026-07-15 12:11:52 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,912,672  ·  17 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

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0x0de29f47…1c06

0x34b655…2a6f

4 touches
1 conflict

0x1bd69a6a…2b8a

0x34b655…2a6f

4 touches
1 conflict

0x2e30c36b…b1fa

0x34b655…2a6f

4 touches
1 conflict

0x3c8d99a5…b937

0x34b655…2a6f

4 touches
1 conflict

0x4327afd2…1b3a

0x34b655…2a6f

4 touches
1 conflict

0x56f59993…2c32

0x34b655…2a6f

4 touches
1 conflict

0x6045a1eb…189e

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 0xc36fa35805…6f24cb

← previous block·next block →recent activity