← previous blocknext block →recent activity

Analyzing

Block #86,960,465

21 transactions · 19 stateful · 2026-07-11 02:03:27 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,960,465  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x16a8cd0c…27bd

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x3904851c…9cad

0x34b655…2a6f

4 touches
1 conflict

0x4caf91f9…8ab5

0x34b655…2a6f

4 touches
1 conflict

0x5238dcb7…e0e2

0x34b655…2a6f

4 touches
1 conflict

0x6d99ac64…0aa3

0x34b655…2a6f

4 touches
1 conflict

0x90e113f8…c8f9

0xc8689a…ee79

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity