← previous blocknext block →recent activity

Analyzing

Block #85,345,728

29 transactions · 20 stateful · 2026-07-03 14:25:10 UTC

Parallelism

86/100

Blocked

40%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,345,728  ·  29 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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x2c506459…5351

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x1c627bf9…d696

0x34b655…2a6f

4 touches
1 conflict

0x342a12bc…c045

0x34b655…2a6f

4 touches
1 conflict

0x56d04b30…74bb

0x34b655…2a6f

4 touches
1 conflict

0x68379acc…f3d8

0x34b655…2a6f

4 touches
1 conflict

0x754c7f04…5673

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 0xfaef08b108…f90696

← previous block·next block →recent activity