← previous blocknext block →recent activity

Analyzing

Block #88,356,054

21 transactions · 17 stateful · 2026-07-17 13:38:17 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #88,356,054  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc1d8201c…3484

0x34b655…2a6f

6 touches
3 conflicts

0x2d3930d3…c9b8

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5800322d…530c

0x34b655…2a6f

4 touches
1 conflict

0x6d955786…1327

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x83762542…18ed

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 0xc1d8201c1c…203484

← previous block·next block →recent activity