← previous blocknext block →recent activity

Analyzing

Block #72,296,638

25 transactions · 23 stateful · 2026-05-04 03:38:34 UTC

Parallelism

68/100

Blocked

70%

Avg conflicts / tx

1.64

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,296,638  ·  25 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

0x6042b6d1…cd47

0xd32edf…ff58

11 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

8 touches
6 conflicts

0x93afca4c…b478

0x1b6862…e19c

8 touches
6 conflicts

0xa0063f79…69a7

0x065c9d…c394

7 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: 0xd32edf66…9fff58

15 conflicts on slot 0x6042b6d14f…9ccd47

← previous block·next block →recent activity