← previous blocknext block →recent activity

Analyzing

Block #88,041,761

17 transactions · 16 stateful · 2026-07-16 02:35:17 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #88,041,761  ·  17 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

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0xbf78ee7f…e7fd

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xb2a25bac…c741

0x34b655…2a6f

6 touches
3 conflicts

0x8b87ece6…3353

0x34b655…2a6f

6 touches
3 conflicts

0x78346476…4311

0x34b655…2a6f

4 touches
1 conflict

0x962b5b93…0ea2

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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

10 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity