← previous blocknext block →recent activity

Analyzing

Block #86,350,176

31 transactions · 22 stateful · 2026-07-08 06:02:27 UTC

Parallelism

84/100

Blocked

27%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,350,176  ·  31 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x006c3b86…59a9

0x34b655…2a6f

4 touches
1 conflict

0x0d2de0f6…e6c6

0x34b655…2a6f

4 touches
1 conflict

0x19530680…4c17

0x34b655…2a6f

4 touches
1 conflict

0x2f0da331…b946

0x34b655…2a6f

4 touches
1 conflict

0x3e505a15…70f8

0x34b655…2a6f

4 touches
1 conflict

0x53baa009…68b3

0x34b655…2a6f

4 touches
1 conflict

0x548145a9…cfce

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity