← previous blocknext block →recent activity

Analyzing

Block #86,281,760

23 transactions · 18 stateful · 2026-07-07 22:25:36 UTC

Parallelism

87/100

Blocked

39%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,281,760  ·  23 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

0xc85f42b6…6f23

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x619ef200…8fed

0x34b655…2a6f

4 touches
1 conflict

0x74fd0a9b…3aaa

0x34b655…2a6f

4 touches
1 conflict

0x79e8f935…c3b6

0x34b655…2a6f

4 touches
1 conflict

0x7e8ebc95…aded

0x34b655…2a6f

4 touches
1 conflict

0x99701186…1cbf

0x34b655…2a6f

4 touches
1 conflict

0xa1571d54…ae41

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 0xc85f42b605…b36f23

← previous block·next block →recent activity