Block #72,224,841

← previous blocknext block →recent activity

Analyzing

Block #72,224,841

7 transactions · 6 stateful · 2026-05-03 19:36:03 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x3610ec01…67b9

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0f7a26f3…5d05

0x065c9d…c394

3 touches
1 conflict

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0xb99b8296…5dd8

0x065c9d…c394

2 touches
0 conflicts

0xe5007bc8…6005

0x065c9d…c394

2 touches
0 conflicts

0xf055d80d…1c68

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 0x3610ec01ee…6b67b9

← previous block·next block →recent activity