Block #72,429,859

← previous blocknext block →recent activity

Analyzing

Block #72,429,859

18 transactions · 14 stateful · 2026-05-04 18:26:09 UTC

Parallelism

89/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,429,859  ·  18 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

0x6eff5416…605d

0xea1b8e…c5ec

4 touches
1 conflict

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x3dbd9177…e936

0xea1b8e…c5ec

3 touches
1 conflict

0x6db2323c…73d5

0x065c9d…c394

2 touches
0 conflicts

0x93521554…6195

0x065c9d…c394

2 touches
0 conflicts

0xa7915a4a…f2b4

0x065c9d…c394

2 touches
0 conflicts

0xe0e33513…1cab

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