← previous blocknext block →recent activity

Analyzing

Block #83,631,233

27 transactions · 23 stateful · 2026-06-25 15:54:35 UTC

Parallelism

78/100

Blocked

35%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,631,233  ·  27 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

0xe99d8e68…a16e

0x34b655…2a6f

12 touches
15 conflicts

0x022f72c3…07b6

0xc8689a…ee79

8 touches
6 conflicts

0x5396d712…a139

0x34b655…2a6f

8 touches
6 conflicts

0x82dd2252…e1ce

0x34b655…2a6f

8 touches
6 conflicts

0xacb30f19…adac

0x34b655…2a6f

8 touches
6 conflicts

0x2cb897e4…21ea

0x34b655…2a6f

7 touches
6 conflicts

0x43c4f03a…e6bb

0x34b655…2a6f

6 touches
3 conflicts

0x9fc8b97d…96da

0x2a68ba…90c5

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