← previous blocknext block →recent activity

Analyzing

Block #84,495,958

19 transactions · 16 stateful · 2026-06-29 15:58:43 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,495,958  ·  19 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

0xb3975d93…b4a2

0x34b655…2a6f

8 touches
6 conflicts

0x8b7cb3cc…95ed

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb84

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xec86d8d9…e3fd

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 0xb3975d9364…28b4a2

← previous block·next block →recent activity