← previous blocknext block →recent activity

Analyzing

Block #82,796,890

35 transactions · 22 stateful · 2026-06-21 18:59:45 UTC

Parallelism

77/100

Blocked

50%

Avg conflicts / tx

1.06

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #82,796,890  ·  35 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

0x482471ad…122f

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0xd3a433e6…2fad

0x34b655…2a6f

8 touches
6 conflicts

0x8b305a3b…1c34

0x34b655…2a6f

8 touches
6 conflicts

0x8b305a3b…1c35

0x34b655…2a6f

8 touches
6 conflicts

0x8eef368f…aa21

0x34b655…2a6f

8 touches
6 conflicts

0x6f132c01…cdcd

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

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

28 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity