← previous blocknext block →recent activity

Analyzing

Block #86,780,516

23 transactions · 16 stateful · 2026-07-10 06:00:34 UTC

Parallelism

83/100

Blocked

50%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,780,516  ·  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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x8d888c90…5479

0x34b655…2a6f

6 touches
3 conflicts

0x69ce640b…884a

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x330a0e84…0d91

0x34b655…2a6f

4 touches
1 conflict

0x352852e1…e791

0x34b655…2a6f

4 touches
1 conflict

0x454cdf57…aebc

0x34b655…2a6f

4 touches
1 conflict

0x4caf91f9…8ab5

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 0xfaef08b108…f90696

← previous block·next block →recent activity