← previous blocknext block →recent activity

Analyzing

Block #83,617,067

23 transactions · 18 stateful · 2026-06-25 14:19:54 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,617,067  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0x8d3f06db…98cb

0x34b655…2a6f

6 touches
3 conflicts

0x785889c9…0603

0x34b655…2a6f

6 touches
3 conflicts

0x233c6f3b…0380

0x34b655…2a6f

6 touches
3 conflicts

0x76477ddf…b8f8

0xc8689a…ee79

4 touches
1 conflict

0x003e3399…a0a5

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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

10 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity