Block #72,226,296

← previous blocknext block →recent activity

Analyzing

Block #72,226,296

8 transactions · 7 stateful · 2026-05-03 19:45:51 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,226,296  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbb601fe7…d0d7

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x14ede7a0…8409

0x065c9d…c394

4 touches
1 conflict

0xf7f33781…b9e3

0x065c9d…c394

4 touches
1 conflict

0x6af16680…78b9

0x065c9d…c394

3 touches
1 conflict

0xc581837c…a181

0x065c9d…c394

3 touches
1 conflict

0xf7ee25bb…4649

0x065c9d…c394

3 touches
1 conflict

0x438cf5f6…f077

0x2a68ba…90c5

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 0xbb601fe788…bad0d7

← previous block·next block →recent activity