← previous blocknext block →recent activity

Analyzing

Block #82,506,245

21 transactions · 20 stateful · 2026-06-20 10:36:40 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

1.14

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,506,245  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

8 touches
6 conflicts

0x33e3dcdd…1f1f

0x34b655…2a6f

6 touches
3 conflicts

0x7e4b5149…c444

0x34b655…2a6f

6 touches
3 conflicts

0xf324b405…ca30

0x34b655…2a6f

4 touches
1 conflict

0x9ff176a9…152e

0x065c9d…c394

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity