← previous blocknext block →recent activity

Analyzing

Block #88,807,773

25 transactions · 24 stateful · 2026-07-19 16:00:42 UTC

Parallelism

84/100

Blocked

25%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,807,773  ·  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

0x5babb0df…9cf9

0x34b655…2a6f

6 touches
3 conflicts

0x56fed0dd…5820

0x34b655…2a6f

6 touches
3 conflicts

0x56fed0dd…581f

0x34b655…2a6f

6 touches
3 conflicts

0x574a8378…b246

0x34b655…2a6f

6 touches
3 conflicts

0xb836e289…93aa

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

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 0x5babb0dfd5…649cf9

← previous block·next block →recent activity