Block #72,371,081

← previous blocknext block →recent activity

Analyzing

Block #72,371,081

8 transactions · 7 stateful · 2026-05-04 11:54:25 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,371,081  ·  8 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

0xef70cad2…dde3

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd895ee0b…d301

0x34b655…2a6f

4 touches
1 conflict

0xd0c49270…5424

0x065c9d…c394

3 touches
1 conflict

0xab13dd56…b48f

0x065c9d…c394

3 touches
1 conflict

0x39432434…a809

0x065c9d…c394

2 touches
0 conflicts

0x520f0a43…7d22

0x065c9d…c394

2 touches
0 conflicts

0xb177968a…389b

0x065c9d…c394

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 0xef70cad289…0bdde3

← previous block·next block →recent activity