← previous blocknext block →recent activity

Analyzing

Block #85,929,567

16 transactions · 12 stateful · 2026-07-06 07:14:21 UTC

Parallelism

81/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,929,567  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x9092da13…341b

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xc978dec7…e3d6

0x34b655…2a6f

4 touches
1 conflict

0x28287367…f0f5

0x34b655…2a6f

4 touches
1 conflict

0x408d584a…8309

0x34b655…2a6f

4 touches
1 conflict

0x427c9fc4…5cee

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

1 conflict on slot 0x9092da13b5…87341b

← previous block·next block →recent activity