← previous blocknext block →recent activity

Analyzing

Block #85,923,794

17 transactions · 12 stateful · 2026-07-06 06:35:53 UTC

Parallelism

88/100

Blocked

25%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #85,923,794  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xafd867b7…2b2e

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x1aaf4996…65ec

0x34b655…2a6f

4 touches
1 conflict

0x86a11e8a…07f7

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x5d4a3441…e31c

0x34b655…2a6f

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

← previous block·next block →recent activity