← previous blocknext block →recent activity

Analyzing

Block #85,919,057

22 transactions · 18 stateful · 2026-07-06 06:04:18 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

0.77

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #85,919,057  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0x517d35c7…f359

0x34b655…2a6f

6 touches
3 conflicts

0xff196840…a453

0x34b655…2a6f

6 touches
3 conflicts

0x3439dfbc…0d03

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6637e421…af93

0x34b655…2a6f

4 touches
1 conflict

0x98e2e7cd…e4c2

0x34b655…2a6f

4 touches
1 conflict

0x9a3463f0…0b73

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity