← previous blocknext block →recent activity

Analyzing

Block #86,298,281

24 transactions · 19 stateful · 2026-07-08 00:15:52 UTC

Parallelism

88/100

Blocked

32%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0xc7f7d98f…cfe7

0x34b655…2a6f

6 touches
3 conflicts

0x2c3dd960…8880

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x329f2f7d…dcff

0x34b655…2a6f

4 touches
1 conflict

0x45333eb3…3e7d

0x34b655…2a6f

4 touches
1 conflict

0x6100906b…8421

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 0xc7f7d98fdd…77cfe7

← previous block·next block →recent activity