← previous blocknext block →recent activity

Analyzing

Block #86,714,092

31 transactions · 16 stateful · 2026-07-09 22:36:48 UTC

Parallelism

84/100

Blocked

50%

Avg conflicts / tx

0.32

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,714,092  ·  31 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x2b955c02…b142

0x065c9d…c394

4 touches
1 conflict

0x52e69143…95ad

0x065c9d…c394

4 touches
1 conflict

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0x0bd95eb4…e562

0x34b655…2a6f

4 touches
1 conflict

0x56b5f5c0…a3ad

0x34b655…2a6f

4 touches
1 conflict

0x59dccbd8…2bf6

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity