← previous blocknext block →recent activity

Analyzing

Block #86,775,655

18 transactions · 12 stateful · 2026-07-10 05:28:11 UTC

Parallelism

83/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,775,655  ·  18 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

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x76ebf9c2…e0ef

0x34b655…2a6f

4 touches
1 conflict

0x97bc6b5d…55ca

0x34b655…2a6f

4 touches
1 conflict

0xe4b8f2c5…f54d

0x34b655…2a6f

4 touches
1 conflict

0x12bc23cf…d56d

0x34b655…2a6f

2 touches
0 conflicts

0x16363afe…d410

0x34b655…2a6f

2 touches
0 conflicts

0x226ae29a…2612

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 0x0733be30d6…38112f

← previous block·next block →recent activity