← previous blocknext block →recent activity

Analyzing

Block #82,975,959

25 transactions · 20 stateful · 2026-06-22 14:56:32 UTC

Parallelism

64/100

Blocked

45%

Avg conflicts / tx

1.28

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #82,975,959  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x96047c45…b64a

0x34b655…2a6f

14 touches
21 conflicts

0x87fd591e…94fa

0x34b655…2a6f

10 touches
10 conflicts

0x08913286…f0df

0x34b655…2a6f

10 touches
10 conflicts

0xb1c67a7d…b9b1

0x34b655…2a6f

10 touches
10 conflicts

0x36a49c16…89b9

0xc8689a…ee79

10 touches
10 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x899a4135…5e49

0x34b655…2a6f

6 touches
3 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 0x96047c45d5…89b64a

← previous block·next block →recent activity