Block #72,284,425

← previous blocknext block →recent activity

Analyzing

Block #72,284,425

18 transactions · 16 stateful · 2026-05-04 02:16:33 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,284,425  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x24cc7fc7…fa3a

0x065c9d…c394

4 touches
1 conflict

0x5af21afc…a0a1

0x065c9d…c394

3 touches
1 conflict

0xb1fba903…6f2b

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity