← previous blocknext block →recent activity

Analyzing

Block #81,634,912

24 transactions · 18 stateful · 2026-06-16 09:44:58 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #81,634,912  ·  24 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

0x90f07a4f…d932

0x34b655…2a6f

8 touches
6 conflicts

0x2484cc15…5afc

0x34b655…2a6f

6 touches
3 conflicts

0x36708245…6bd9

0x34b655…2a6f

6 touches
3 conflicts

0x4f4bdabd…ffba

0x34b655…2a6f

6 touches
3 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x712729d5…0f31

0x34b655…2a6f

6 touches
3 conflicts

0x7202d831…318a

0x34b655…2a6f

6 touches
3 conflicts

0x7babfe9a…ff96

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 0x90f07a4ff9…b3d932

← previous block·next block →recent activity