← previous blocknext block →recent activity

Analyzing

Block #88,138,275

20 transactions · 18 stateful · 2026-07-16 13:20:51 UTC

Parallelism

60/100

Blocked

56%

Avg conflicts / tx

1.2

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #88,138,275  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x9465204c…bf37

0x34b655…2a6f

12 touches
15 conflicts

0x9022951d…ef43

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x4a5956ef…e226

0x34b655…2a6f

4 touches
1 conflict

0x66bdb4c2…7ea6

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

15 conflicts on slot 0x9465204cd8…debf37

← previous block·next block →recent activity