← previous blocknext block →recent activity

Analyzing

Block #88,358,866

23 transactions · 22 stateful · 2026-07-17 13:57:14 UTC

Parallelism

57/100

Blocked

45%

Avg conflicts / tx

1.91

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #88,358,866  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x22e0cc1d…ad0d

0x34b655…2a6f

14 touches
21 conflicts

0x326a02b5…8dad

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xb9834665…e363

0x34b655…2a6f

8 touches
6 conflicts

0x07b47a10…27ef

0x34b655…2a6f

8 touches
6 conflicts

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

21 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity