← previous blocknext block →recent activity

Analyzing

Block #85,918,656

21 transactions · 17 stateful · 2026-07-06 06:01:38 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,918,656  ·  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

0xafd867b7…2b2d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1aaf4996…65ec

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x28f40bdb…42f9

0x34b655…2a6f

4 touches
1 conflict

0x29c1a140…099f

0x34b655…2a6f

4 touches
1 conflict

0x353a3a00…5e0a

0x34b655…2a6f

4 touches
1 conflict

0x3cf50d44…961b

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 0xafd867b7ed…d92b2d

← previous block·next block →recent activity