Block #72,224,802

← previous blocknext block →recent activity

Analyzing

Block #72,224,802

9 transactions · 7 stateful · 2026-05-03 19:35:48 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,224,802  ·  9 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

0x580d4ecd…f90f

0x065c9d…c394

4 touches
1 conflict

0x7e02032a…c07b

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5656d18c…0b32

0x065c9d…c394

3 touches
1 conflict

0xd8a5018a…44c9

0x065c9d…c394

3 touches
1 conflict

0x86681db6…6d0f

0x065c9d…c394

2 touches
0 conflicts

0x88493668…480b

0x065c9d…c394

2 touches
0 conflicts

0xd79b26d7…8497

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 0x580d4ecd63…16f90f

← previous block·next block →recent activity