← previous blocknext block →recent activity

Analyzing

Block #86,486,494

21 transactions · 18 stateful · 2026-07-08 21:13:38 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,486,494  ·  21 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

0xda2ee2e7…968a

0x34b655…2a6f

6 touches
3 conflicts

0x51d373d5…fb08

0x34b655…2a6f

4 touches
1 conflict

0x52163873…f09f

0x34b655…2a6f

4 touches
1 conflict

0x7bc74ef3…0fee

0x34b655…2a6f

4 touches
1 conflict

0x7d2645cd…5d8e

0x34b655…2a6f

4 touches
1 conflict

0x7ee6007b…fd68

0x34b655…2a6f

4 touches
1 conflict

0x9f40a209…1193

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