← previous blocknext block →recent activity

Analyzing

Block #83,479,775

21 transactions · 16 stateful · 2026-06-24 23:04:05 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,479,775  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x8d0e1d29…cd3e

0x34b655…2a6f

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x40970e69…da50

0x69df8a…6292

6 touches
3 conflicts

0x8cf3d245…1d0d

0x69df8a…6292

6 touches
3 conflicts

0xb05cd4f5…73d0

0x69df8a…6292

6 touches
3 conflicts

0xdb067026…9eb8

0x69df8a…6292

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

6 conflicts on slot 0x8d0e1d2905…4ecd3e

← previous block·next block →recent activity