Block #72,310,032

← previous blocknext block →recent activity

Analyzing

Block #72,310,032

38 transactions · 27 stateful · 2026-05-04 05:07:49 UTC

Parallelism

79/100

Blocked

52%

Avg conflicts / tx

0.68

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,310,032  ·  38 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

8 touches
6 conflicts

0x746365e3…8e32

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0xd5a25205…6458

0x1b6862…e19c

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

6 conflicts on slot 0xf823e97fa0…262ee6

← previous block·next block →recent activity