← previous blocknext block →recent activity

Analyzing

Block #84,559,651

15 transactions · 13 stateful · 2026-06-29 23:03:56 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,559,651  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xec1d7176…6f5e

0x34b655…2a6f

6 touches
3 conflicts

0x0aaf1c6f…f3bd

0x34b655…2a6f

4 touches
1 conflict

0x0ddcdb60…fed4

0x34b655…2a6f

4 touches
1 conflict

0x3cbb66ce…0e6d

0x34b655…2a6f

4 touches
1 conflict

0x49f6ddba…b7de

0x34b655…2a6f

4 touches
1 conflict

0x5eeea918…8147

0x34b655…2a6f

4 touches
1 conflict

0x63c900f4…2600

0x34b655…2a6f

4 touches
1 conflict

0x6b47245e…a342

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 0xec1d7176e6…a86f5e

← previous block·next block →recent activity