← previous blocknext block →recent activity

Analyzing

Block #87,489,253

16 transactions · 14 stateful · 2026-07-13 12:58:58 UTC

Parallelism

81/100

Blocked

21%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,489,253  ·  16 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

0x88adad52…54b7

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x96bfa04d…d06b

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xdd34d27a…83e4

0x34b655…2a6f

4 touches
1 conflict

0xfcad4d96…c690

0x34b655…2a6f

4 touches
1 conflict

0xfcad4d96…c691

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

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 0x88adad5202…7d54b7

← previous block·next block →recent activity