← previous blocknext block →recent activity

Analyzing

Block #84,399,996

25 transactions · 19 stateful · 2026-06-29 05:18:58 UTC

Parallelism

84/100

Blocked

37%

Avg conflicts / tx

0.32

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,399,996  ·  25 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

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x76477ddf…b8f8

0xc8689a…ee79

4 touches
1 conflict

0xa9db7b4d…2957

0x40c49f…2af0

4 touches
1 conflict

0xdd9727bf…c04e

0x40c49f…2af0

4 touches
1 conflict

0xdfc5f346…7b42

0x40c49f…2af0

4 touches
1 conflict

0x5da4ed2f…283f

0xa6afd3…d132

4 touches
1 conflict

0x31aa2853…8dbb

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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 0xe99d8e683a…2ea16e

← previous block·next block →recent activity