← previous blocknext block →recent activity

Analyzing

Block #82,758,028

25 transactions · 21 stateful · 2026-06-21 14:40:24 UTC

Parallelism

72/100

Blocked

71%

Avg conflicts / tx

1.44

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,758,028  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x76d1e78d…7877

0x40c49f…2af0

12 touches
15 conflicts

0x00000000…003d

0x40c49f…2af0

10 touches
10 conflicts

0x5581d709…ab77

0x2a68ba…90c5

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x5d46e6a0…5ed9

0x40c49f…2af0

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x96047c45…b64a

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: 0x40c49f17…d22af0

15 conflicts on slot 0x76d1e78d12…117877

← previous block·next block →recent activity