← previous blocknext block →recent activity

Analyzing

Block #87,524,909

24 transactions · 22 stateful · 2026-07-13 16:58:08 UTC

Parallelism

79/100

Blocked

32%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,524,909  ·  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

0xffc2f21e…b393

0x34b655…2a6f

8 touches
6 conflicts

0x864353d4…dcb7

0x34b655…2a6f

6 touches
3 conflicts

0x1b2c54a1…5a76

0x34b655…2a6f

4 touches
2 conflicts

0x4e10224d…58d3

0x34b655…2a6f

4 touches
1 conflict

0x548145a9…cfce

0x34b655…2a6f

4 touches
1 conflict

0x63c900f4…2600

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x8a238c35…ca08

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 0xffc2f21efe…ecb393

← previous block·next block →recent activity