← previous blocknext block →recent activity

Analyzing

Block #83,641,645

23 transactions · 16 stateful · 2026-06-25 17:04:09 UTC

Parallelism

74/100

Blocked

56%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,641,645  ·  23 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

0xffb1ee54…7c2c

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x7e6c970a…65af

0x34b655…2a6f

6 touches
3 conflicts

0x845d95c8…db0f

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

6 touches
3 conflicts

0x9fbabe09…8dd6

0x34b655…2a6f

6 touches
3 conflicts

0xa1e51cc8…e4cf

0x34b655…2a6f

6 touches
3 conflicts

0xb1c67a7d…b9b1

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

6 conflicts on slot 0xffb1ee5457…d07c2c

← previous block·next block →recent activity