← previous blocknext block →recent activity

Analyzing

Block #87,716,978

21 transactions · 20 stateful · 2026-07-14 14:22:53 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,716,978  ·  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

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xbf78ee7f…e7fd

0x34b655…2a6f

6 touches
3 conflicts

0xfef0ce0a…aa80

0x34b655…2a6f

4 touches
1 conflict

0x7a8cad7f…48cd

0x34b655…2a6f

4 touches
1 conflict

0x8eedf936…a0c3

0x34b655…2a6f

4 touches
1 conflict

0xb9eb13f6…33c3

0x34b655…2a6f

4 touches
1 conflict

0xc5f336ca…912e

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 0x0733be30d6…38112f

← previous block·next block →recent activity