← previous blocknext block →recent activity

Analyzing

Block #84,489,800

22 transactions · 19 stateful · 2026-06-29 15:17:36 UTC

Parallelism

82/100

Blocked

37%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,489,800  ·  22 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

0x13c5b486…d41e

0x34b655…2a6f

6 touches
3 conflicts

0x454d8940…cfe7

0x34b655…2a6f

6 touches
3 conflicts

0x28a5dbb8…3ad7

0x34b655…2a6f

6 touches
3 conflicts

0x76639fd3…a13f

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x8725f80c…ff6e

0x1b6862…e19c

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

3 conflicts on slot 0x13c5b4868d…1ad41e

← previous block·next block →recent activity