Block #72,365,788

← previous blocknext block →recent activity

Analyzing

Block #72,365,788

6 transactions · 5 stateful · 2026-05-04 11:19:12 UTC

Parallelism

50/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,365,788  ·  6 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x347dbd18…e622

0x065c9d…c394

2 touches
0 conflicts

0x367ce492…deb1

0x065c9d…c394

2 touches
0 conflicts

0x5d5740ff…14d1

0x065c9d…c394

2 touches
0 conflicts

0x7a655b7c…db10

0x065c9d…c394

2 touches
0 conflicts

0x8085a40b…eb4f

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity