← previous blocknext block →recent activity

Analyzing

Block #88,807,026

17 transactions · 16 stateful · 2026-07-19 15:55:43 UTC

Parallelism

82/100

Blocked

25%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,807,026  ·  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

0x7907f7f7…dc3f

0x34b655…2a6f

4 touches
1 conflict

0x90fefe5e…f0c6

0x34b655…2a6f

4 touches
1 conflict

0x92793b0e…b68e

0x34b655…2a6f

4 touches
1 conflict

0xa279b18d…63bc

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xf75bd49b…581b

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x4fe848d9…9077

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x7907f7f764…8adc3f

← previous block·next block →recent activity