← previous blocknext block →recent activity

Analyzing

Block #84,259,530

20 transactions · 17 stateful · 2026-06-28 13:42:42 UTC

Parallelism

80/100

Blocked

35%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,259,530  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x7e17e82a…9748

0x34b655…2a6f

6 touches
3 conflicts

0x925c118c…a1d8

0x34b655…2a6f

6 touches
3 conflicts

0xd064a456…b881

0x34b655…2a6f

6 touches
3 conflicts

0xe732567d…b65d

0x34b655…2a6f

6 touches
3 conflicts

0xf324b405…ca30

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x32409e80…a396

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity