← previous blocknext block →recent activity

Analyzing

Block #86,657,857

22 transactions · 18 stateful · 2026-07-09 16:21:33 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

0.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,657,857  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a7

0xb1dbf0…c0d3

6 touches
3 conflicts

0x8a35acfb…d1a8

0xb1dbf0…c0d3

6 touches
3 conflicts

0x63b15849…80b2

0x34b655…2a6f

4 touches
1 conflict

0x6bc490c3…315c

0x34b655…2a6f

4 touches
1 conflict

0x727fbce7…0c80

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 0xc824469a90…af6425

← previous block·next block →recent activity