Block #72,400,080

← previous blocknext block →recent activity

Analyzing

Block #72,400,080

10 transactions · 7 stateful · 2026-05-04 15:07:45 UTC

Parallelism

70/100

Blocked

29%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,400,080  ·  10 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

0xf282d38a…cfae

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4180871b…a6f6

0x065c9d…c394

3 touches
1 conflict

0xab5b883d…417f

0x065c9d…c394

3 touches
1 conflict

0xab5b883d…4180

0x065c9d…c394

3 touches
1 conflict

0xa8ac0767…13de

0x065c9d…c394

2 touches
0 conflicts

0x05eea3e3…5846

0x2a68ba…90c5

2 touches
0 conflicts

0x74e71984…ae90

0x2a68ba…90c5

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 0xf282d38ae9…24cfae

← previous block·next block →recent activity