← previous blocknext block →recent activity

Analyzing

Block #72,859,837

28 transactions · 21 stateful · 2026-05-06 18:11:38 UTC

Parallelism

82/100

Blocked

57%

Avg conflicts / tx

1.07

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,859,837  ·  28 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

0x3b8ffd61…f3ad

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xfd175e2e…5fa5

0xd32edf…ff58

9 touches
10 conflicts

0x59658b83…2229

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x0520da1d…c88e

0x34b655…2a6f

6 touches
3 conflicts

0x085df2c1…305a

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: 0x34b6552d…112a6f

10 conflicts on slot 0x3b8ffd6160…92f3ad

← previous block·next block →recent activity