← previous blocknext block →recent activity

Analyzing

Block #83,628,495

34 transactions · 20 stateful · 2026-06-25 15:36:18 UTC

Parallelism

88/100

Blocked

35%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,628,495  ·  34 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

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0xe02484a6…c32e

0xc8689a…ee79

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x8d3f06db…98cb

0x34b655…2a6f

6 touches
3 conflicts

0xacb576ad…e0a1

0x34b655…2a6f

6 touches
3 conflicts

0xfd4e2262…cd8c

0x34b655…2a6f

4 touches
1 conflict

0x2cb897e4…21ea

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

6 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity