Block #72,271,737

← previous blocknext block →recent activity

Analyzing

Block #72,271,737

7 transactions · 7 stateful · 2026-05-04 00:51:17 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,271,737  ·  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

0xe6f3ee49…2cdb

0x065c9d…c394

4 touches
1 conflict

0x3d4bcef4…57e6

0x065c9d…c394

4 touches
1 conflict

0x70c52e91…0824

0x065c9d…c394

3 touches
1 conflict

0xaa8d1e7e…0871

0x065c9d…c394

3 touches
1 conflict

0xcf1e7466…73e3

0x065c9d…c394

3 touches
1 conflict

0x5809da19…8f28

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x84b4e4b9…417f

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 0xe6f3ee4960…272cdb

← previous block·next block →recent activity