← previous blocknext block →recent activity

Analyzing

Block #86,298,364

21 transactions · 20 stateful · 2026-07-08 00:16:25 UTC

Parallelism

71/100

Blocked

45%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,298,364  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x3659eace…e64e

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x0bd95eb4…e562

0x34b655…2a6f

6 touches
3 conflicts

0x1ca2c9cd…8f8e

0x34b655…2a6f

4 touches
1 conflict

0x1d9867ad…6d9a

0x34b655…2a6f

4 touches
1 conflict

0x2007b9af…3c71

0x34b655…2a6f

4 touches
1 conflict

0x310b36c6…6c03

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

← previous block·next block →recent activity