← previous blocknext block →recent activity

Analyzing

Block #85,366,579

23 transactions · 22 stateful · 2026-07-03 16:44:09 UTC

Parallelism

78/100

Blocked

36%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,366,579  ·  23 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

6 touches
3 conflicts

0xa20a130c…5d59

0x34b655…2a6f

6 touches
3 conflicts

0x0cd285d6…1676

0x34b655…2a6f

4 touches
1 conflict

0x17792361…4d4c

0x34b655…2a6f

4 touches
1 conflict

0x1b70c852…0ddb

0x34b655…2a6f

4 touches
1 conflict

0x23253ea8…e0a4

0x34b655…2a6f

4 touches
1 conflict

0x2d071de0…c86e

0x34b655…2a6f

4 touches
1 conflict

0x4126374d…bee1

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

← previous block·next block →recent activity