Block #72,296,250

← previous blocknext block →recent activity

Analyzing

Block #72,296,250

13 transactions · 11 stateful · 2026-05-04 03:35:58 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,296,250  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xcfdd426c…0a1b

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x08c69d87…2adc

0x065c9d…c394

3 touches
1 conflict

0x2a454362…8401

0x065c9d…c394

3 touches
1 conflict

0x729c91b8…9539

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0000

0x1c5f9a…bcc5

2 touches
0 conflicts

0x00000000…0002

0x1c5f9a…bcc5

2 touches
0 conflicts

0x00000000…0003

0x1c5f9a…bcc5

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

1 conflict on slot 0xcfdd426cbe…7d0a1b

← previous block·next block →recent activity