← previous blocknext block →recent activity

Analyzing

Block #86,686,204

18 transactions · 18 stateful · 2026-07-09 19:30:45 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,686,204  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x63c900f4…2600

0x34b655…2a6f

6 touches
3 conflicts

0x727fbce7…0c80

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xf324b405…ca30

0x34b655…2a6f

6 touches
3 conflicts

0x7017d770…abbd

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1a9

0xb1dbf0…c0d3

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: Settlement / Helper

3 conflicts on slot 0x922c7ebd9c…1c6600

← previous block·next block →recent activity