← previous blocknext block →recent activity

Analyzing

Block #82,975,916

25 transactions · 19 stateful · 2026-06-22 14:56:15 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,975,916  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x08913286…f0df

0x34b655…2a6f

12 touches
15 conflicts

0x36a49c16…89b9

0xc8689a…ee79

8 touches
6 conflicts

0xb1c67a7d…b9b1

0x34b655…2a6f

8 touches
6 conflicts

0x96047c45…b64a

0x34b655…2a6f

8 touches
6 conflicts

0x87fd591e…94fa

0x34b655…2a6f

8 touches
6 conflicts

0x6ae06ca0…85b5

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

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

15 conflicts on slot 0x08913286f9…0ff0df

← previous block·next block →recent activity