← previous blocknext block →recent activity

Analyzing

Block #88,074,928

23 transactions · 22 stateful · 2026-07-16 06:17:05 UTC

Parallelism

83/100

Blocked

23%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,074,928  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x8d5fc820…1750

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x0d2e1791…c1dd

0x34b655…2a6f

4 touches
1 conflict

0x560b6fd9…a104

0x34b655…2a6f

4 touches
1 conflict

0x5e06ddb0…0bb0

0x34b655…2a6f

4 touches
1 conflict

0x883e9a5b…0f01

0x34b655…2a6f

4 touches
1 conflict

0xa7efa115…74f3

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity