← previous blocknext block →recent activity

Analyzing

Block #88,185,494

20 transactions · 19 stateful · 2026-07-16 18:37:25 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,185,494  ·  20 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

8 touches
6 conflicts

0x923c57f1…7810

0x34b655…2a6f

6 touches
3 conflicts

0xa50fcb98…2b01

0x34b655…2a6f

6 touches
3 conflicts

0xa88d5ae7…6495

0x34b655…2a6f

6 touches
3 conflicts

0x00ddbbf2…4588

0x34b655…2a6f

6 touches
3 conflicts

0xcf610ab1…35ad

0x34b655…2a6f

5 touches
3 conflicts

0x367b69ad…33d9

0x34b655…2a6f

4 touches
1 conflict

0x458b9085…9ee2

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

← previous block·next block →recent activity