← previous blocknext block →recent activity

Analyzing

Block #85,763,557

14 transactions · 8 stateful · 2026-07-05 12:48:31 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,763,557  ·  14 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

0x0ab54c30…b88e

0x34b655…2a6f

6 touches
3 conflicts

0xddd7607e…9b4b

0x34b655…2a6f

4 touches
1 conflict

0x05b1b07a…7a99

0x34b655…2a6f

4 touches
1 conflict

0x1d720942…075a

0x34b655…2a6f

4 touches
1 conflict

0x2148d664…e4c5

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x98834cc0…6c23

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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 0x0ab54c30a6…82b88e

← previous block·next block →recent activity