Block #72,314,683

← previous blocknext block →recent activity

Analyzing

Block #72,314,683

7 transactions · 7 stateful · 2026-05-04 05:38:46 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,314,683  ·  7 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xcccabc14…cbe4

0x065c9d…c394

4 touches
1 conflict

0x9a2478c0…fd7f

0x065c9d…c394

3 touches
1 conflict

0x505c9f8d…6810

0x065c9d…c394

3 touches
1 conflict

0x35323df1…7129

0x065c9d…c394

2 touches
0 conflicts

0x466589ac…3249

0x065c9d…c394

2 touches
0 conflicts

0xb63fede2…2857

0x065c9d…c394

2 touches
0 conflicts

0xd3db58c0…0929

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 0x0000000000…00003d

← previous block·next block →recent activity