← previous blocknext block →recent activity

Analyzing

Block #85,159,693

19 transactions · 17 stateful · 2026-07-02 17:46:07 UTC

Parallelism

63/100

Blocked

47%

Avg conflicts / tx

1.32

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,159,693  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x32409e80…a396

0x34b655…2a6f

4 touches
1 conflict

0x4384dd01…4f99

0x34b655…2a6f

4 touches
1 conflict

0x6637e421…af93

0x34b655…2a6f

4 touches
1 conflict

0x6bdb9869…7558

0x34b655…2a6f

4 touches
1 conflict

0x97b0b2ee…4666

0x34b655…2a6f

4 touches
1 conflict

0x9a573905…60cf

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity