← previous blocknext block →recent activity

Analyzing

Block #87,705,672

24 transactions · 21 stateful · 2026-07-14 13:07:04 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

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

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0xfe3d2a2f…6b7b

0x34b655…2a6f

4 touches
1 conflict

0x1526b11f…8b21

0x34b655…2a6f

4 touches
1 conflict

0x3661e3af…9170

0x34b655…2a6f

4 touches
1 conflict

0x505b37d8…d3fc

0x34b655…2a6f

4 touches
1 conflict

0x70b7b52e…7743

0x34b655…2a6f

4 touches
1 conflict

0x70b7b52e…7744

0x34b655…2a6f

4 touches
1 conflict

0xa38eb2fc…1659

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity