← previous blocknext block →recent activity

Analyzing

Block #88,139,524

21 transactions · 20 stateful · 2026-07-16 13:29:13 UTC

Parallelism

81/100

Blocked

40%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,139,524  ·  21 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

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x250c3574…21db

0x851145…3f07

6 touches
3 conflicts

0x77fb04fd…9db8

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xa11c8c34…fbca

0x34b655…2a6f

6 touches
3 conflicts

0xd330c0c5…6f64

0x34b655…2a6f

6 touches
3 conflicts

0xfb979525…6d4d

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

6 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity