← previous blocknext block →recent activity

Analyzing

Block #85,027,397

20 transactions · 19 stateful · 2026-07-02 03:01:53 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,027,397  ·  20 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

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x03fb27fd…0c06

0x34b655…2a6f

4 touches
1 conflict

0x35dc4075…74c2

0x34b655…2a6f

4 touches
1 conflict

0x7523ad90…2ba5

0x34b655…2a6f

4 touches
1 conflict

0x989dd242…26f2

0x34b655…2a6f

4 touches
1 conflict

0x9f40a209…1193

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

3 conflicts on slot 0xffc2f21efe…ecb393

← previous block·next block →recent activity