← previous blocknext block →recent activity

Analyzing

Block #83,634,009

29 transactions · 19 stateful · 2026-06-25 16:13:08 UTC

Parallelism

90/100

Blocked

32%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,634,009  ·  29 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4bdcc5ee…7e90

0x34b655…2a6f

4 touches
1 conflict

0x5906754f…b584

0x34b655…2a6f

4 touches
1 conflict

0x8bfb4e08…df1e

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x7b7af531…48f1

0xa6afd3…d132

4 touches
1 conflict

0x4bb3539b…b005

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity