← previous blocknext block →recent activity

Analyzing

Block #87,504,801

24 transactions · 19 stateful · 2026-07-13 14:43:03 UTC

Parallelism

79/100

Blocked

32%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,504,801  ·  24 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

0x8bf661cb…bcd2

0x34b655…2a6f

8 touches
6 conflicts

0x13ed417e…a863

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x15c83c9d…5b94

0x34b655…2a6f

4 touches
1 conflict

0x326f2a00…a2a6

0x34b655…2a6f

4 touches
1 conflict

0x4fbbd9b3…c1c0

0x34b655…2a6f

4 touches
1 conflict

0x5140ab8f…34da

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0x8bf661cb38…d4bcd2

← previous block·next block →recent activity