← previous blocknext block →recent activity

Analyzing

Block #86,617,294

22 transactions · 18 stateful · 2026-07-09 11:49:14 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,617,294  ·  22 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

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x32409e80…a396

0x34b655…2a6f

6 touches
3 conflicts

0x3e505a15…70f8

0x34b655…2a6f

4 touches
1 conflict

0x57e03cb3…d7bb

0x34b655…2a6f

4 touches
1 conflict

0x60c7217a…8c94

0x34b655…2a6f

4 touches
1 conflict

0x64aaadbf…f9f3

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 0xea02471df2…601542

← previous block·next block →recent activity