← previous blocknext block →recent activity

Analyzing

Block #88,365,767

17 transactions · 15 stateful · 2026-07-17 14:43:48 UTC

Parallelism

88/100

Blocked

7%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #88,365,767  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x1ee91407…f0f2

0x34b655…2a6f

4 touches
1 conflict

0x26444b91…765e

0x34b655…2a6f

4 touches
1 conflict

0xb25fa8e2…c9ef

0x34b655…2a6f

4 touches
1 conflict

0xb454e863…177f

0x34b655…2a6f

4 touches
1 conflict

0x363a4317…87d2

0x34b655…2a6f

4 touches
1 conflict

0x9c4bf061…1101

0x34b655…2a6f

4 touches
1 conflict

0x821f0b86…7ebb

0x34b655…2a6f

3 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

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity