← previous blocknext block →recent activity

Analyzing

Block #86,665,817

22 transactions · 17 stateful · 2026-07-09 17:14:37 UTC

Parallelism

77/100

Blocked

47%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,665,817  ·  22 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

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0xca2926e0…61b5

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1aa

0xb1dbf0…c0d3

6 touches
3 conflicts

0x0e9a70ab…e67c

0x34b655…2a6f

6 touches
3 conflicts

0x289f9358…7567

0x34b655…2a6f

4 touches
1 conflict

0x554b9217…5959

0x34b655…2a6f

4 touches
1 conflict

0x9365e097…ff56

0x34b655…2a6f

4 touches
1 conflict

0x94e7f277…471b

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

10 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity