← previous blocknext block →recent activity

Analyzing

Block #88,358,155

18 transactions · 18 stateful · 2026-07-17 13:52:28 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

1.11

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #88,358,155  ·  18 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

0xebac0f82…a49c

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x02991b41…19e6

0x34b655…2a6f

6 touches
3 conflicts

0xda46a376…f6a6

0x34b655…2a6f

6 touches
3 conflicts

0x720bad39…0419

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x87ee379a…cd9e

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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

6 conflicts on slot 0xebac0f82ec…86a49c

← previous block·next block →recent activity