← previous blocknext block →recent activity

Analyzing

Block #72,271,401

5 transactions · 5 stateful · 2026-05-04 00:49:02 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,271,401  ·  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

0xbc70d921…d885

0x065c9d…c394

4 touches
1 conflict

0x379cf9a8…f0fa

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x49bad189…6264

0x065c9d…c394

4 touches
1 conflict

0x21264d60…4039

0x065c9d…c394

3 touches
1 conflict

0xca30243e…1ec7

0x065c9d…c394

3 touches
1 conflict

0x9db0a49f…7fe7

0x065c9d…c394

3 touches
1 conflict

0x39252e2a…9cda

0x065c9d…c394

3 touches
1 conflict

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 0xbc70d921aa…66d885

← previous block·next block →recent activity