← previous blocknext block →recent activity

Analyzing

Block #85,145,523

25 transactions · 22 stateful · 2026-07-02 16:11:45 UTC

Parallelism

68/100

Blocked

41%

Avg conflicts / tx

1.16

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #85,145,523  ·  25 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

14 touches
21 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xf3d10975…0d07

0x34b655…2a6f

10 touches
10 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

8 touches
6 conflicts

0x6bdb9869…7558

0x34b655…2a6f

8 touches
6 conflicts

0xded5ec0c…f0fc

0x34b655…2a6f

6 touches
3 conflicts

0x6a53b1c0…c3f2

0x34b655…2a6f

4 touches
1 conflict

0xf28082df…312c

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