Block #72,296,379

← previous blocknext block →recent activity

Analyzing

Block #72,296,379

5 transactions · 5 stateful · 2026-05-04 03:36:50 UTC

Parallelism

60/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,296,379  ·  5 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

0x760e9c05…f4ca

0x065c9d…c394

4 touches
1 conflict

0x08012a78…50c2

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x99a3b976…8ad9

0x065c9d…c394

3 touches
1 conflict

0x037bb43d…92b4

0x065c9d…c394

3 touches
1 conflict

0x11b9474e…f282

0x065c9d…c394

2 touches
0 conflicts

0x5ea474f4…9697

0x065c9d…c394

2 touches
0 conflicts

0xbb1f6c94…3ca5

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 0x760e9c0556…3df4ca

← previous block·next block →recent activity