← previous blocknext block →recent activity

Analyzing

Block #86,845,256

21 transactions · 19 stateful · 2026-07-10 13:13:20 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,845,256  ·  21 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

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

6 touches
3 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

6 touches
3 conflicts

0x63c900f4…2600

0x34b655…2a6f

6 touches
3 conflicts

0x851ff3c1…1b15

0x34b655…2a6f

6 touches
3 conflicts

0x9f40a209…1193

0x34b655…2a6f

6 touches
3 conflicts

0xb4aa41e0…f123

0x34b655…2a6f

6 touches
3 conflicts

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 0x92385428ad…dc6941

← previous block·next block →recent activity