← previous blocknext block →recent activity

Analyzing

Block #85,847,267

18 transactions · 14 stateful · 2026-07-05 22:06:08 UTC

Parallelism

83/100

Blocked

36%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,847,267  ·  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

0xb1939b09…99dd

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0369789f…1922

0x34b655…2a6f

4 touches
1 conflict

0x11431f9d…42c5

0x34b655…2a6f

4 touches
1 conflict

0x1544d128…23e7

0x34b655…2a6f

4 touches
1 conflict

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x24b878bb…874c

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

3 conflicts on slot 0xb1939b09eb…d499dd

← previous block·next block →recent activity