← previous blocknext block →recent activity

Analyzing

Block #88,080,022

12 transactions · 11 stateful · 2026-07-16 06:51:10 UTC

Parallelism

67/100

Blocked

55%

Avg conflicts / tx

0.83

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,080,022  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x64aaadbf…f9f3

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x0dd44476…ef40

0x34b655…2a6f

4 touches
1 conflict

0x1191dbf7…8e85

0x34b655…2a6f

4 touches
1 conflict

0x2c344031…cc71

0x34b655…2a6f

4 touches
1 conflict

0x50718952…7c75

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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

6 conflicts on slot 0x64aaadbf0a…79f9f3

← previous block·next block →recent activity