← previous blocknext block →recent activity

Analyzing

Block #86,484,558

24 transactions · 23 stateful · 2026-07-08 21:00:43 UTC

Parallelism

71/100

Blocked

35%

Avg conflicts / tx

0.75

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,484,558  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xd35bb5ac…3586

0x065c9d…c394

4 touches
1 conflict

0x01c969a3…227b

0x34b655…2a6f

4 touches
1 conflict

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x4118d6f0…e297

0x34b655…2a6f

4 touches
1 conflict

0x451f5977…7300

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

10 conflicts on slot 0xc948dbdcb8…f4199a

← previous block·next block →recent activity