← previous blocknext block →recent activity

Analyzing

Block #87,620,308

14 transactions · 12 stateful · 2026-07-14 03:36:15 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,620,308  ·  14 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

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x20fbcaee…bb79

0x34b655…2a6f

4 touches
1 conflict

0x3f85f288…7c97

0x34b655…2a6f

4 touches
1 conflict

0x49f75237…44f4

0x34b655…2a6f

4 touches
1 conflict

0x4a5956ef…e226

0x34b655…2a6f

4 touches
1 conflict

0x548145a9…cfce

0x34b655…2a6f

4 touches
1 conflict

0x73ca2093…8dd6

0x34b655…2a6f

4 touches
1 conflict

0x8dbfdaf6…6925

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity