← previous blocknext block →recent activity

Analyzing

Block #82,667,747

48 transactions · 37 stateful · 2026-06-21 04:37:32 UTC

Parallelism

71/100

Blocked

76%

Avg conflicts / tx

2.96

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #82,667,747  ·  48 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

22 touches
55 conflicts

0x5fcfa433…c999

0xd32edf…ff58

15 touches
28 conflicts

0x08913286…f0df

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0028

0x1b6862…e19c

10 touches
10 conflicts

0x93afca4c…b478

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 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

55 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity