← previous blocknext block →recent activity

Analyzing

Block #83,642,283

23 transactions · 21 stateful · 2026-06-25 17:08:25 UTC

Parallelism

70/100

Blocked

43%

Avg conflicts / tx

0.91

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,642,283  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

6 touches
3 conflicts

0x7e6c970a…65af

0x34b655…2a6f

6 touches
3 conflicts

0x965b1522…eefa

0x34b655…2a6f

6 touches
3 conflicts

0x9b58e20f…2dd9

0x34b655…2a6f

6 touches
3 conflicts

0xb1c67a7d…b9b1

0x34b655…2a6f

6 touches
3 conflicts

0xbfe63d66…c3e6

0x34b655…2a6f

6 touches
3 conflicts

0xf324b405…ca30

0x34b655…2a6f

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

15 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity