← previous blocknext block →recent activity

Analyzing

Block #84,574,097

23 transactions · 20 stateful · 2026-06-30 00:40:20 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,574,097  ·  23 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

0x4384dd01…4f99

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0d177e65…6831

0x34b655…2a6f

4 touches
1 conflict

0x32b67841…b758

0x34b655…2a6f

4 touches
1 conflict

0x374fc18a…6998

0x34b655…2a6f

4 touches
1 conflict

0x5d7f309d…5145

0x34b655…2a6f

4 touches
1 conflict

0x712f13a9…bee0

0x34b655…2a6f

4 touches
1 conflict

0x9ad4d28a…c788

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

3 conflicts on slot 0x4384dd01db…564f99

← previous block·next block →recent activity