← previous blocknext block →recent activity

Analyzing

Block #83,454,985

23 transactions · 20 stateful · 2026-06-24 20:18:36 UTC

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

0.96

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,454,985  ·  23 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

0xe99d8e68…a16e

0x34b655…2a6f

12 touches
15 conflicts

0x3ec82b22…1f46

0x34b655…2a6f

10 touches
10 conflicts

0xdf37a93d…879b

0x34b655…2a6f

8 touches
6 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

8 touches
6 conflicts

0xd08b8a31…0998

0x34b655…2a6f

8 touches
6 conflicts

0x022f72c3…07b6

0xc8689a…ee79

8 touches
6 conflicts

0x10a2bf7d…caf7

0x34b655…2a6f

6 touches
3 conflicts

0x61eca0dc…2aba

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

15 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity