← previous blocknext block →recent activity

Analyzing

Block #86,920,495

25 transactions · 19 stateful · 2026-07-10 21:36:22 UTC

Parallelism

88/100

Blocked

26%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,920,495  ·  25 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xc948dbdc…199a

0x34b655…2a6f

6 touches
3 conflicts

0x7d42dc8b…fdb6

0x2a68ba…90c5

4 touches
1 conflict

0x65e795ca…0320

0x34b655…2a6f

4 touches
1 conflict

0x69ca0810…e942

0x34b655…2a6f

4 touches
1 conflict

0x6b7a4e91…8284

0x34b655…2a6f

4 touches
1 conflict

0x78d79dcd…a930

0x34b655…2a6f

4 touches
1 conflict

0x78d79dcd…a931

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4ab

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

3 conflicts on slot 0xc948dbdcb8…f4199a

← previous block·next block →recent activity