← previous blocknext block →recent activity

Analyzing

Block #86,675,322

12 transactions · 11 stateful · 2026-07-09 18:18:06 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

0.83

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,675,322  ·  12 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xcfe88c6a…0758

0x34b655…2a6f

4 touches
1 conflict

0x9fd372a1…a959

0x34b655…2a6f

4 touches
1 conflict

0x9e70dadd…810e

0x34b655…2a6f

4 touches
1 conflict

0x9e70dadd…810d

0x34b655…2a6f

4 touches
1 conflict

0x13699f68…7491

0x34b655…2a6f

4 touches
1 conflict

0x59e4ffbf…f01b

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 0x482471adbb…39122f

← previous block·next block →recent activity