← previous blocknext block →recent activity

Analyzing

Block #88,082,528

23 transactions · 19 stateful · 2026-07-16 07:07:54 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,082,528  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x52163873…f09f

0x34b655…2a6f

6 touches
3 conflicts

0x310afe2c…83e1

0x34b655…2a6f

4 touches
1 conflict

0x5f3d8ec8…7c13

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0xb1e4ea6c…3e29

0x34b655…2a6f

4 touches
1 conflict

0xd972ea45…48b5

0x34b655…2a6f

4 touches
1 conflict

0xda6ebfcf…d51e

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity