← previous blocknext block →recent activity

Analyzing

Block #86,850,692

26 transactions · 20 stateful · 2026-07-10 13:49:38 UTC

Parallelism

81/100

Blocked

40%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,850,692  ·  26 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf81d0d0f…cf78

0x34b655…2a6f

6 touches
3 conflicts

0xa279b18d…63bc

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd2771e4d…705d

0x34b655…2a6f

6 touches
3 conflicts

0x94bb14fe…8f47

0x34b655…2a6f

4 touches
1 conflict

0xf0783775…7b62

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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