← previous blocknext block →recent activity

Analyzing

Block #72,233,076

33 transactions · 26 stateful · 2026-05-03 20:31:28 UTC

Parallelism

79/100

Blocked

58%

Avg conflicts / tx

0.88

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,233,076  ·  33 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xce8bbe33…b72e

0x3bd359…433a

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x17046be4…ac80

0xd32edf…ff58

7 touches
6 conflicts

0xef446fe1…57c8

0x065c9d…c394

7 touches
6 conflicts

0x00000000…001f

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: 0x3bd359c1…15433a

6 conflicts on slot 0xce8bbe3367…8cb72e

← previous block·next block →recent activity