← previous blocknext block →recent activity

Analyzing

Block #82,974,998

22 transactions · 20 stateful · 2026-06-22 14:50:07 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.05

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #82,974,998  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x08913286…f0df

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x05c3e030…9b48

0x34b655…2a6f

6 touches
3 conflicts

0x505d32fe…14ad

0x34b655…2a6f

6 touches
3 conflicts

0x510c8ab3…95d5

0x34b655…2a6f

6 touches
3 conflicts

0xb1c67a7d…b9b1

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity