← previous blocknext block →recent activity

Analyzing

Block #88,091,435

25 transactions · 20 stateful · 2026-07-16 08:07:29 UTC

Parallelism

80/100

Blocked

35%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #88,091,435  ·  25 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x38d0c21b…9b5b

0x34b655…2a6f

4 touches
1 conflict

0x3f85f288…7c97

0x34b655…2a6f

4 touches
1 conflict

0x5777bd87…71bd

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xee75c266…f8c6

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