← previous blocknext block →recent activity

Analyzing

Block #85,774,815

27 transactions · 22 stateful · 2026-07-05 14:03:29 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,774,815  ·  27 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

10 touches
10 conflicts

0x1b8a880a…5ce4

0x34b655…2a6f

6 touches
3 conflicts

0xcdc1731c…b91a

0x34b655…2a6f

6 touches
3 conflicts

0x1eb0fab5…3517

0x34b655…2a6f

4 touches
1 conflict

0x309ef367…e8a1

0x34b655…2a6f

4 touches
1 conflict

0x5a27ab8f…74ca

0x34b655…2a6f

4 touches
1 conflict

0x75f928fc…0465

0x34b655…2a6f

4 touches
1 conflict

0x7e17e82a…9748

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