← previous blocknext block →recent activity

Analyzing

Block #87,723,362

20 transactions · 20 stateful · 2026-07-14 15:05:34 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,723,362  ·  20 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

0x64a058c6…74a1

0x34b655…2a6f

6 touches
3 conflicts

0x043a73f8…f7e9

0x34b655…2a6f

4 touches
1 conflict

0x0f12a71f…17a5

0x34b655…2a6f

4 touches
1 conflict

0x131a4489…c12c

0x34b655…2a6f

4 touches
1 conflict

0x19805670…b4f4

0x34b655…2a6f

4 touches
1 conflict

0x1f2cd70b…94be

0x34b655…2a6f

4 touches
1 conflict

0x1fbe3441…7d6f

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

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 0x64a058c6c8…5774a1

← previous block·next block →recent activity