← previous blocknext block →recent activity

Analyzing

Block #84,060,449

39 transactions · 20 stateful · 2026-06-27 15:36:55 UTC

Parallelism

87/100

Blocked

35%

Avg conflicts / tx

0.36

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,060,449  ·  39 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x31aa2853…8dbb

0xc8689a…ee79

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x0efc210e…70ab

0x34b655…2a6f

6 touches
3 conflicts

0x26731ffc…6b25

0x34b655…2a6f

6 touches
3 conflicts

0xe1e58d05…117f

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x213ee207…a151

0x69df8a…6292

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

10 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity