← previous blocknext block →recent activity

Analyzing

Block #86,787,933

16 transactions · 12 stateful · 2026-07-10 06:50:06 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,787,933  ·  16 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

0xf2f4727d…cdb7

0x34b655…2a6f

6 touches
3 conflicts

0xa523c16d…15cd

0x34b655…2a6f

4 touches
1 conflict

0xab774675…75f7

0x34b655…2a6f

4 touches
1 conflict

0xbb277c58…e388

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x0ae9d2df…f788

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 0xf2f4727df6…a5cdb7

← previous block·next block →recent activity