← previous blocknext block →recent activity

Analyzing

Block #88,075,841

17 transactions · 15 stateful · 2026-07-16 06:23:11 UTC

Parallelism

82/100

Blocked

47%

Avg conflicts / tx

0.59

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,075,841  ·  17 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

0x0dd44476…ef40

0x34b655…2a6f

6 touches
3 conflicts

0x71892c70…660d

0x34b655…2a6f

6 touches
3 conflicts

0x9e70dadd…810d

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc4412023…7a5b

0x34b655…2a6f

6 touches
3 conflicts

0x8ff87fa9…2410

0x34b655…2a6f

5 touches
3 conflicts

0x4c86a6b8…7f9f

0x34b655…2a6f

4 touches
1 conflict

0x506e543d…0b67

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 0x0dd44476b8…7fef40

← previous block·next block →recent activity