← previous blocknext block →recent activity

Analyzing

Block #85,128,963

27 transactions · 23 stateful · 2026-07-02 14:21:13 UTC

Parallelism

67/100

Blocked

39%

Avg conflicts / tx

1.04

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #85,128,963  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xe47478a3…a058

0x34b655…2a6f

12 touches
15 conflicts

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

12 touches
15 conflicts

0x922c7ebd…6600

0xc8689a…ee79

12 touches
15 conflicts

0xf3fbc9b8…ab58

0x34b655…2a6f

12 touches
15 conflicts

0x7d3d69b4…4004

0x34b655…2a6f

8 touches
6 conflicts

0x1a2b9063…9752

0x34b655…2a6f

8 touches
6 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0xe47478a3e7…67a058

← previous block·next block →recent activity