← previous blocknext block →recent activity

Analyzing

Block #88,139,319

16 transactions · 15 stateful · 2026-07-16 13:27:51 UTC

Parallelism

81/100

Blocked

13%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,139,319  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xabba7bd6…826a

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xadad6c2d…65c8

0x34b655…2a6f

4 touches
1 conflict

0xd0f6f4f2…dffa

0x34b655…2a6f

4 touches
1 conflict

0x36890fff…f3d1

0x34b655…2a6f

4 touches
1 conflict

0x6aeb45e9…c0f2

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 0x92385428ad…dc6941

← previous block·next block →recent activity