← previous blocknext block →recent activity

Analyzing

Block #84,237,804

21 transactions · 20 stateful · 2026-06-28 11:18:07 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,237,804  ·  21 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xbd68c7c7…40b3

0x34b655…2a6f

6 touches
3 conflicts

0xff96dc9b…93d7

0x065c9d…c394

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x206f4379…e08a

0x34b655…2a6f

4 touches
1 conflict

0x20e57a61…028c

0x34b655…2a6f

4 touches
1 conflict

0x3c53b5ed…9103

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 0xc824469a90…af6425

← previous block·next block →recent activity