← previous blocknext block →recent activity

Analyzing

Block #84,253,588

35 transactions · 30 stateful · 2026-06-28 13:03:12 UTC

Parallelism

77/100

Blocked

60%

Avg conflicts / tx

1.71

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #84,253,588  ·  35 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

14 touches
21 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

12 touches
15 conflicts

0xdfc5f346…7b42

0x40c49f…2af0

10 touches
10 conflicts

0x00000000…003d

0x40c49f…2af0

10 touches
10 conflicts

0x31aa2853…8dbb

0xc8689a…ee79

8 touches
6 conflicts

0x0efc210e…70ab

0x34b655…2a6f

8 touches
6 conflicts

0xd7e72076…294a

0x34b655…2a6f

8 touches
6 conflicts

0xe1e58d05…117f

0x34b655…2a6f

8 touches
6 conflicts

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

21 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity