← previous blocknext block →recent activity

Analyzing

Block #85,176,152

20 transactions · 17 stateful · 2026-07-02 19:35:37 UTC

Parallelism

65/100

Blocked

41%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,176,152  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x765cd07a…1018

0x34b655…2a6f

6 touches
3 conflicts

0x1bee5aea…5f61

0x34b655…2a6f

4 touches
1 conflict

0xfefb0189…f726

0x34b655…2a6f

4 touches
1 conflict

0x12c6929d…e7db

0x34b655…2a6f

4 touches
1 conflict

0xa678cd56…4fab

0x34b655…2a6f

4 touches
1 conflict

0xa800bb04…1d40

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…7212

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity