← previous blocknext block →recent activity

Analyzing

Block #88,357,542

21 transactions · 16 stateful · 2026-07-17 13:48:22 UTC

Parallelism

86/100

Blocked

38%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,357,542  ·  21 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

0x114324a9…6d5e

0x34b655…2a6f

4 touches
1 conflict

0x1fa402f7…7d13

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x4c04ce68…d007

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x9365e097…ff56

0x34b655…2a6f

4 touches
1 conflict

0x9b03f35d…168c

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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

1 conflict on slot 0x114324a9e9…dd6d5e

← previous block·next block →recent activity