← previous blocknext block →recent activity

Analyzing

Block #86,707,920

24 transactions · 21 stateful · 2026-07-09 21:55:36 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,707,920  ·  24 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xa3ed5a09…c6d3

0x34b655…2a6f

6 touches
3 conflicts

0xf1345bef…5530

0x34b655…2a6f

6 touches
3 conflicts

0x1c03f81f…b303

0x34b655…2a6f

4 touches
1 conflict

0x1c03f81f…b304

0x34b655…2a6f

4 touches
1 conflict

0x43c2fa32…4d82

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

6 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity