← previous blocknext block →recent activity

Analyzing

Block #88,358,599

20 transactions · 20 stateful · 2026-07-17 13:55:27 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #88,358,599  ·  20 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x02991b41…19e6

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x69a64a5c…0000

0x34b655…2a6f

6 touches
3 conflicts

0x6cf4c1b0…1422

0x065c9d…c394

5 touches
3 conflicts

0xfaf22814…27c8

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 0xc824469a90…af6425

← previous block·next block →recent activity