← previous blocknext block →recent activity

Analyzing

Block #86,822,547

7 transactions · 6 stateful · 2026-07-10 10:41:33 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,822,547  ·  7 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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xa07e7b13…7513

0x34b655…2a6f

4 touches
1 conflict

0xf83b23f9…5a2e

0x34b655…2a6f

4 touches
1 conflict

0xf83b23f9…5a2f

0x34b655…2a6f

4 touches
1 conflict

0x519c3aa0…08b0

0x34b655…2a6f

4 touches
1 conflict

0x889f0954…da52

0x34b655…2a6f

2 touches
0 conflicts

0x9068a9bc…86ee

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity