Block #72,399,779

← previous blocknext block →recent activity

Analyzing

Block #72,399,779

15 transactions · 14 stateful · 2026-05-04 15:05:45 UTC

Parallelism

67/100

Blocked

36%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,399,779  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x8c09924d…38c8

0xd32edf…ff58

5 touches
3 conflicts

0x26cc676b…a3b3

0x065c9d…c394

5 touches
3 conflicts

0x912d3740…d136

0x065c9d…c394

4 touches
1 conflict

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity