← previous blocknext block →recent activity

Analyzing

Block #85,169,375

24 transactions · 17 stateful · 2026-07-02 18:50:31 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,169,375  ·  24 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

0xd99b3b64…1c95

0x34b655…2a6f

6 touches
3 conflicts

0xfd2c2d84…ef69

0x34b655…2a6f

4 touches
1 conflict

0x076c1a94…3401

0x34b655…2a6f

4 touches
1 conflict

0x0e5f2a94…4732

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x23778a1f…dec4

0x34b655…2a6f

4 touches
1 conflict

0x2c75ca93…a569

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity