← previous blocknext block →recent activity

Analyzing

Block #86,790,281

25 transactions · 24 stateful · 2026-07-10 07:05:44 UTC

Parallelism

84/100

Blocked

29%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,790,281  ·  25 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x7da2eb43…cde7

0x34b655…2a6f

6 touches
3 conflicts

0x96047c45…b64a

0x34b655…2a6f

6 touches
3 conflicts

0xa4e5e0c2…6e04

0x34b655…2a6f

6 touches
3 conflicts

0xc368d7fd…aaec

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity