← previous blocknext block →recent activity

Analyzing

Block #85,133,324

21 transactions · 18 stateful · 2026-07-02 14:50:23 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,133,324  ·  21 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

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x1853f465…3255

0x34b655…2a6f

4 touches
1 conflict

0x18e7fb22…a29f

0x34b655…2a6f

4 touches
1 conflict

0x1d61a1c5…9fe6

0x34b655…2a6f

4 touches
1 conflict

0x25e3730b…24a9

0x34b655…2a6f

4 touches
1 conflict

0x765cd07a…1018

0x34b655…2a6f

4 touches
1 conflict

0x7b3da897…b268

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