← previous blocknext block →recent activity

Analyzing

Block #72,284,833

31 transactions · 24 stateful · 2026-05-04 02:19:18 UTC

Parallelism

87/100

Blocked

46%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,284,833  ·  31 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

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0x005fb969…2d97

0x34b655…2a6f

8 touches
6 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

8 touches
6 conflicts

0x183b7456…e175

0x34b655…2a6f

8 touches
6 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

8 touches
6 conflicts

0x2877f440…c2c8

0x34b655…2a6f

8 touches
6 conflicts

0x3254d19b…f714

0x34b655…2a6f

8 touches
6 conflicts

0x414e9446…4b59

0x34b655…2a6f

8 touches
6 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: 0x065c9d28…a9c394

6 conflicts on slot 0xbbee74c2e7…6e567a

← previous block·next block →recent activity