← previous blocknext block →recent activity

Analyzing

Block #85,127,021

19 transactions · 18 stateful · 2026-07-02 14:08:15 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,127,021  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x3e505a15…70f8

0x34b655…2a6f

6 touches
3 conflicts

0x3c1c2955…df4b

0x34b655…2a6f

4 touches
1 conflict

0x59645a97…3ca1

0x34b655…2a6f

4 touches
1 conflict

0x66227ce6…32eb

0x34b655…2a6f

4 touches
1 conflict

0x7799aca7…bb76

0x34b655…2a6f

4 touches
1 conflict

0x79b3209b…f766

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity