← previous blocknext block →recent activity

Analyzing

Block #86,798,379

21 transactions · 16 stateful · 2026-07-10 07:59:50 UTC

Parallelism

71/100

Blocked

56%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,798,379  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xc3688185…9b36

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd30f9e74…d404

0x34b655…2a6f

6 touches
3 conflicts

0xf83b23f9…5a2e

0x34b655…2a6f

6 touches
3 conflicts

0xf83b23f9…5a2f

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

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 0x737acb7813…fafce8

← previous block·next block →recent activity