← previous blocknext block →recent activity

Analyzing

Block #91,998,532

16 transactions · 16 stateful · 2026-07-31 19:23:33 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.63

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,998,532  ·  16 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

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x177211e2…1c2d

0x754704…b603

6 touches
3 conflicts

0xe1f61186…e2f8

0x754704…b603

6 touches
3 conflicts

0x00000000…0006

0x7b9256…1fb2

6 touches
3 conflicts

0x4c90da18…bfbc

0x7b9256…1fb2

6 touches
3 conflicts

0x4c90da18…bfbd

0x7b9256…1fb2

6 touches
3 conflicts

0x4c90da18…bfc0

0x7b9256…1fb2

6 touches
3 conflicts

0xe219cf61…502e

0x7b9256…1fb2

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

3 conflicts on slot 0x737acb7813…fafce8

← previous block·next block →recent activity