← previous blocknext block →recent activity

Analyzing

Block #88,081,887

21 transactions · 19 stateful · 2026-07-16 07:03:38 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #88,081,887  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xceba0b65…6afe

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x05ae4d3e…3c79

0x34b655…2a6f

4 touches
1 conflict

0x08cc68a2…2a59

0x34b655…2a6f

4 touches
1 conflict

0x25bdc7e4…b92e

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity