Block #72,498,073

← previous blocknext block →recent activity

Analyzing

Block #72,498,073

6 transactions · 4 stateful · 2026-05-05 02:00:25 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,498,073  ·  6 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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0e6eca45…3678

0x065c9d…c394

2 touches
0 conflicts

0x3e1c59af…64c6

0x065c9d…c394

2 touches
0 conflicts

0x613a7157…07e8

0x065c9d…c394

2 touches
0 conflicts

0x81fd68b0…3589

0x065c9d…c394

2 touches
0 conflicts

0x94eaf7ec…6dca

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity