Block #72,977,874

← previous blocknext block →recent activity

Analyzing

Block #72,977,874

10 transactions · 9 stateful · 2026-05-07 07:17:16 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,977,874  ·  10 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

0xc1db956a…1d5d

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x333a92f1…2c3f

0x065c9d…c394

3 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x1c3cb6d6…3f74

0x065c9d…c394

2 touches
0 conflicts

0x5108dbea…d3d5

0x065c9d…c394

2 touches
0 conflicts

0xb0fb357d…0185

0x065c9d…c394

2 touches
0 conflicts

0xd5f3cec0…0cd1

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 0xc1db956a5c…fe1d5d

← previous block·next block →recent activity