← previous blocknext block →recent activity

Analyzing

Block #88,083,012

21 transactions · 20 stateful · 2026-07-16 07:11:09 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #88,083,012  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0xd526c4bd…dbf2

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x94b46bd0…e95d

0x34b655…2a6f

6 touches
3 conflicts

0xb550abea…2729

0x34b655…2a6f

6 touches
3 conflicts

0x0dd44476…ef40

0x34b655…2a6f

6 touches
3 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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity