← previous blocknext block →recent activity

Analyzing

Block #86,632,770

23 transactions · 19 stateful · 2026-07-09 13:32:39 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,632,770  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc0eb79d1…29a4

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

6 touches
3 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

4 touches
1 conflict

0x60c7217a…8c94

0x34b655…2a6f

4 touches
1 conflict

0x63c900f4…2600

0x34b655…2a6f

4 touches
1 conflict

0x727fbce7…0c80

0x34b655…2a6f

4 touches
1 conflict

0x7506443a…4820

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 0xc0eb79d1cb…5529a4

← previous block·next block →recent activity