← previous blocknext block →recent activity

Analyzing

Block #85,605,976

17 transactions · 15 stateful · 2026-07-04 19:18:12 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,605,976  ·  17 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

8 touches
6 conflicts

0x64c57c87…5e42

0x34b655…2a6f

6 touches
3 conflicts

0x7012e9c1…f525

0x34b655…2a6f

6 touches
3 conflicts

0x532023a5…d800

0xe52b14…7230

4 touches
1 conflict

0x8ffa3328…ce11

0xe52b14…7230

4 touches
1 conflict

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0x5fcb4c60…8775

0x34b655…2a6f

4 touches
1 conflict

0x5149ba0e…d954

0x754704…b603

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

← previous block·next block →recent activity