← previous blocknext block →recent activity

Analyzing

Block #86,850,294

24 transactions · 22 stateful · 2026-07-10 13:46:59 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,850,294  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xa37e64f8…ba05

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x3be33cca…0fff

0x34b655…2a6f

4 touches
1 conflict

0x3be33cca…1000

0x34b655…2a6f

4 touches
1 conflict

0x410b84ab…1dbc

0x34b655…2a6f

4 touches
1 conflict

0x17c44db3…8888

0xa6afd3…d132

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity