Block #72,309,837

← previous blocknext block →recent activity

Analyzing

Block #72,309,837

12 transactions · 10 stateful · 2026-05-04 05:06:31 UTC

Parallelism

83/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,309,837  ·  12 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

0x71520b1c…6b8c

0x065c9d…c394

4 touches
1 conflict

0x14c40ee1…c17a

0x065c9d…c394

3 touches
1 conflict

0x1e371e0f…e11b

0x065c9d…c394

3 touches
1 conflict

0x7b43f938…3650

0x000000…012a

2 touches
0 conflicts

0x5f5a65a8…3acc

0x065c9d…c394

2 touches
0 conflicts

0x770927fe…1b33

0x065c9d…c394

2 touches
0 conflicts

0xe08412ed…0bef

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