← previous blocknext block →recent activity

Analyzing

Block #88,351,614

30 transactions · 22 stateful · 2026-07-17 13:08:18 UTC

Parallelism

77/100

Blocked

41%

Avg conflicts / tx

0.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #88,351,614  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xda46a376…f6a6

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x02991b41…19e6

0x34b655…2a6f

6 touches
3 conflicts

0x86482eb1…64ce

0x34b655…2a6f

4 touches
1 conflict

0x87d4be93…1646

0x34b655…2a6f

4 touches
1 conflict

0x87ee379a…cd9e

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

6 conflicts on slot 0xda46a376d7…59f6a6

← previous block·next block →recent activity