← previous blocknext block →recent activity

Analyzing

Block #72,296,695

9 transactions · 7 stateful · 2026-05-04 03:38:56 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,296,695  ·  9 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

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xe3808c30…a7d5

0x065c9d…c394

5 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…0006

0x0a439a…0e3c

2 touches
0 conflicts

0x00000000…0007

0x0a439a…0e3c

2 touches
0 conflicts

0x00000000…000f

0x0a439a…0e3c

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…000d

0x1b6862…e19c

2 touches
0 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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity