← previous blocknext block →recent activity

Analyzing

Block #88,342,878

25 transactions · 22 stateful · 2026-07-17 12:09:50 UTC

Parallelism

84/100

Blocked

27%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,342,878  ·  25 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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x3a7fb5b5…f0e5

0x34b655…2a6f

6 touches
3 conflicts

0xca125b62…fb1c

0x34b655…2a6f

6 touches
3 conflicts

0x9a964905…d410

0x34b655…2a6f

5 touches
3 conflicts

0xdb067026…9eb8

0x2b46c0…1669

4 touches
1 conflict

0x06eb454c…0ef9

0x34b655…2a6f

4 touches
1 conflict

0x18a3a88d…3c12

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