← previous blocknext block →recent activity

Analyzing

Block #87,597,010

21 transactions · 16 stateful · 2026-07-14 01:00:31 UTC

Parallelism

86/100

Blocked

38%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,597,010  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x10024ba0…4587

0x34b655…2a6f

4 touches
1 conflict

0x2170bea4…4722

0x34b655…2a6f

4 touches
1 conflict

0x2170bea4…4723

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x3bb514bf…2967

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x68a28395…228b

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

1 conflict on slot 0x10024ba071…0c4587

← previous block·next block →recent activity