← previous blocknext block →recent activity

Analyzing

Block #83,454,273

21 transactions · 18 stateful · 2026-06-24 20:13:51 UTC

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,454,273  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x03fb27fd…0c06

0x34b655…2a6f

8 touches
6 conflicts

0x022f72c3…07b6

0xc8689a…ee79

8 touches
6 conflicts

0xffb1ee54…7c2c

0x34b655…2a6f

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0xdf37a93d…879b

0x34b655…2a6f

8 touches
6 conflicts

0x72bbdcc6…69ae

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

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 0x03fb27fddd…f00c06

← previous block·next block →recent activity