← previous blocknext block →recent activity

Analyzing

Block #88,080,411

21 transactions · 19 stateful · 2026-07-16 06:53:46 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #88,080,411  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

4 touches
1 conflict

0x23778a1f…dec4

0x34b655…2a6f

4 touches
1 conflict

0x2e30c36b…b1fa

0x34b655…2a6f

4 touches
1 conflict

0x49f6ddba…b7de

0x34b655…2a6f

4 touches
1 conflict

0x4f1ad4b4…e00a

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 0x92385428ad…dc6941

← previous block·next block →recent activity