← previous blocknext block →recent activity

Analyzing

Block #88,082,906

17 transactions · 16 stateful · 2026-07-16 07:10:26 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,082,906  ·  17 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

0x5777bd87…71bd

0x34b655…2a6f

6 touches
3 conflicts

0x23778a1f…dec4

0x34b655…2a6f

4 touches
1 conflict

0x3d4584df…ffed

0x34b655…2a6f

4 touches
1 conflict

0x3fd08a81…bd5c

0x34b655…2a6f

4 touches
1 conflict

0x43603f1e…c190

0x34b655…2a6f

4 touches
1 conflict

0x43b571b0…a8ae

0x34b655…2a6f

4 touches
1 conflict

0x57330c5d…9973

0x34b655…2a6f

4 touches
1 conflict

0xffb8950c…23c6

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 0x5777bd874f…7071bd

← previous block·next block →recent activity