← previous blocknext block →recent activity

Analyzing

Block #86,249,875

28 transactions · 16 stateful · 2026-07-07 18:52:49 UTC

Parallelism

86/100

Blocked

38%

Avg conflicts / tx

0.32

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,249,875  ·  28 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x6a9e408e…3721

0x34b655…2a6f

6 touches
3 conflicts

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0x5230f914…fa48

0x34b655…2a6f

4 touches
1 conflict

0x65903ef9…2567

0x34b655…2a6f

4 touches
1 conflict

0x74fa9cc0…c570

0x34b655…2a6f

4 touches
1 conflict

0x84fb2a36…db89

0x34b655…2a6f

4 touches
1 conflict

0x9a291a56…9a9c

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