← previous blocknext block →recent activity

Analyzing

Block #84,572,942

21 transactions · 18 stateful · 2026-06-30 00:32:36 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,572,942  ·  21 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

0xd99b3b64…1c95

0x34b655…2a6f

8 touches
6 conflicts

0x7f93f2f0…6666

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7585925a…3f45

0x34b655…2a6f

5 touches
3 conflicts

0x6eb3e5af…064e

0x34b655…2a6f

4 touches
1 conflict

0x8b1b058b…0435

0x34b655…2a6f

4 touches
1 conflict

0x97c67486…27fe

0x34b655…2a6f

4 touches
1 conflict

0x9966da31…0d0f

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

6 conflicts on slot 0xd99b3b6441…7a1c95

← previous block·next block →recent activity